Package 0x3a5c…d811
Package0x3a5c…d811
Package details
- Project
- Not labelled
- Version
- 1 of 1
- Publisher
- 0x9dfc…1d63Address0x9dfc0fb0fab7955eda4965942d6a561bd987515706aa2e83ae3018ef8c1b1d63LabelNone known
- Package ID
- 0x3a5c…d811
- Published
- Upgrade policy
Compatible?
The holder of the upgrade cap can publish new versions. A new version must keep every public function signature and struct layout, so existing callers keep working.
- Upgrade cap
- 0x0e54…e23aObject0x0e540c813908d48ac246106ad8d4c4d2e0b73e923254599fec539e2f8fa1e23a
- Cap holder
- 0x9dfc…1d63Address0x9dfc0fb0fab7955eda4965942d6a561bd987515706aa2e83ae3018ef8c1b1d63LabelNone known
- Source
- Not verified
- Storage deposit
- 0.4360652 SUI
- Publish tx
- 3DJDzL…kfVS
Modules
1 functions, 0 public, 1 structs
| Module | Public functions | Entry functions | Structs | Constants | Friend modules | |
|---|---|---|---|---|---|---|
| mattn_series_2 | 0 | 0 | 1 | 5 |
Upgrade history
Every upgrade publishes a new package with its own ID. All versions share the original ID (version 1's) 0x3a5c…d811, and the version number counts up, so the highest number is the current code.
A transaction names the exact package ID it calls, so older versions can still be called unless the package itself refuses them, often with a version check on a shared object.
A type keeps the ID of the version that first defined it. Types from version 1 use the original ID for good, while a type added in a later upgrade uses that version's ID.
| Version | Package ID | Time | By | Transaction | Calls, 7 days | |
|---|---|---|---|---|---|---|
| Version 1LatestPublished | 0x3a5c…d811 | 0x9dfc…1d63Address0x9dfc0fb0fab7955eda4965942d6a561bd987515706aa2e83ae3018ef8c1b1d63LabelNone known | 3DJDzL…kfVS | … |
Recent calls
Reading recent calls
Dependencies
The exact versions this package was linked against
| Package | Package ID | Original ID | Linked version | |
|---|---|---|---|---|
| Move Stdlib | 0x0000…0001 | Same | 16 | |
| Sui Framework | 0x0000…0002 | Same | 34 |