Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c72caccfb457dd9fef582ff9c07f1334e69016d58a24bea9cfd7fc8b3b3293e5

Tx prefix hash: 8821c46ca690de8e23b6e91c7475b14e95f8ee92b776a462219fa314878f3d6b
Tx public key: 7d7ff983c9c6112d87013764bf8b42afa7ffff28c50aad7f3db0906e23b85e7b
Timestamp: 1758743789 Timestamp [UCT]: 2025-09-24 19:56:29 Age [y:d:h:m:s]: 00:126:18:41:33
Block: 1375649 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90594 RingCT/type: yes/0
Extra: 017d7ff983c9c6112d87013764bf8b42afa7ffff28c50aad7f3db0906e23b85e7b02110000000cb2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: edd1de2e6336fc5dd4382a63aef68b9fd1f62ead425abca8c7604a34a383c3d8 0.600000000000 1863740 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": 1375659, "vin": [ { "gen": { "height": 1375649 } } ], "vout": [ { "amount": 600000000, "target": { "key": "edd1de2e6336fc5dd4382a63aef68b9fd1f62ead425abca8c7604a34a383c3d8" } } ], "extra": [ 1, 125, 127, 249, 131, 201, 198, 17, 45, 135, 1, 55, 100, 191, 139, 66, 175, 167, 255, 255, 40, 197, 10, 173, 127, 61, 176, 144, 110, 35, 184, 94, 123, 2, 17, 0, 0, 0, 12, 178, 247, 132, 196, 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