Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 451977c06b1a3d55f97568700664f9347f128ebbf2a1838498c947caa42a0fa6

Tx prefix hash: 8529b40908a6792e994b4e708b40b8c2e7d7d1fe6521863c3d2f587b093943f9
Tx public key: 0c1cddf0acbd8ddb8a2ba9c80b73444728b0ea6ed13e3c858ba53f8a27e3bc77
Timestamp: 1719591032 Timestamp [UCT]: 2024-06-28 16:10:32 Age [y:d:h:m:s]: 00:285:11:19:36
Block: 1054154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203995 RingCT/type: yes/0
Extra: 010c1cddf0acbd8ddb8a2ba9c80b73444728b0ea6ed13e3c858ba53f8a27e3bc770211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49aa37e28ddd5525fdeb30c2fedbc3dfa93a462ac762ce9607a0b4606c5434ea 0.600000000000 1524513 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": 1054164, "vin": [ { "gen": { "height": 1054154 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49aa37e28ddd5525fdeb30c2fedbc3dfa93a462ac762ce9607a0b4606c5434ea" } } ], "extra": [ 1, 12, 28, 221, 240, 172, 189, 141, 219, 138, 43, 169, 200, 11, 115, 68, 71, 40, 176, 234, 110, 209, 62, 60, 133, 139, 165, 63, 138, 39, 227, 188, 119, 2, 17, 0, 0, 0, 1, 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