Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cca663bf7cbf936e72dfbf09110da25a4636f1abdbeb9e87be60849c6965ff15

Tx prefix hash: bb44da88a5d6e98d667b96e3d4b996e990311989861956e04d27d7874d0dc100
Tx public key: 3ce9f00d7692a5cda8e74c92395f69ae824071906b8aaef693d529ff5d51e8a5
Timestamp: 1720555569 Timestamp [UCT]: 2024-07-09 20:06:09 Age [y:d:h:m:s]: 00:227:15:55:15
Block: 1062167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162598 RingCT/type: yes/0
Extra: 013ce9f00d7692a5cda8e74c92395f69ae824071906b8aaef693d529ff5d51e8a502110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 28ef33b1079eeafe1eb0477b26ca61c0c65b57712c6d07288d211ef9a5a44296 0.600000000000 1532668 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": 1062177, "vin": [ { "gen": { "height": 1062167 } } ], "vout": [ { "amount": 600000000, "target": { "key": "28ef33b1079eeafe1eb0477b26ca61c0c65b57712c6d07288d211ef9a5a44296" } } ], "extra": [ 1, 60, 233, 240, 13, 118, 146, 165, 205, 168, 231, 76, 146, 57, 95, 105, 174, 130, 64, 113, 144, 107, 138, 174, 246, 147, 213, 41, 255, 93, 81, 232, 165, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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