Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 56dcc4a0f9ab2ae87d84b031c464e57c85efea9d95d6516d6b459b47de232721

Tx prefix hash: d4335c93791375af517f85790d106dcee4beac9b615853d5dc54db5835a5d647
Tx public key: 7d67650048adb8e1f87bd512f3d41a085309a4acb780c9fa64eb8d499edba809
Timestamp: 1711680201 Timestamp [UCT]: 2024-03-29 02:43:21 Age [y:d:h:m:s]: 01:008:09:02:13
Block: 988596 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266937 RingCT/type: yes/0
Extra: 017d67650048adb8e1f87bd512f3d41a085309a4acb780c9fa64eb8d499edba8090211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71ff9a119e9ea6b7a6075c774c7d23b7949a54b67b46978ff7f97f93890925e4 0.600000000000 1448875 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 988606, "vin": [ { "gen": { "height": 988596 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71ff9a119e9ea6b7a6075c774c7d23b7949a54b67b46978ff7f97f93890925e4" } } ], "extra": [ 1, 125, 103, 101, 0, 72, 173, 184, 225, 248, 123, 213, 18, 243, 212, 26, 8, 83, 9, 164, 172, 183, 128, 201, 250, 100, 235, 141, 73, 158, 219, 168, 9, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8