Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc4b3356db0d382f19c809e3138f0330ed7cd3d3dabb342910a11f21ca070a29

Tx prefix hash: 296d130d91aaebbb48498e13ab262e68b3a02ec4ad5ae357fd9d951e29774874
Tx public key: b42fec2c59b5ab30c39e76daccf7aa390164bdeaa60634cf9796c1e336fbb987
Timestamp: 1749388197 Timestamp [UCT]: 2025-06-08 13:09:57 Age [y:d:h:m:s]: 00:165:22:51:23
Block: 1300651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116282 RingCT/type: yes/0
Extra: 01b42fec2c59b5ab30c39e76daccf7aa390164bdeaa60634cf9796c1e336fbb987021100000001bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd9943566c0dbde2d1a169a940748f01af1db4aa7521a67b95fd8b088382c1b3 0.600000000000 1788200 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": 1300661, "vin": [ { "gen": { "height": 1300651 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd9943566c0dbde2d1a169a940748f01af1db4aa7521a67b95fd8b088382c1b3" } } ], "extra": [ 1, 180, 47, 236, 44, 89, 181, 171, 48, 195, 158, 118, 218, 204, 247, 170, 57, 1, 100, 189, 234, 166, 6, 52, 207, 151, 150, 193, 227, 54, 251, 185, 135, 2, 17, 0, 0, 0, 1, 191, 81, 178, 162, 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