Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 706982a24bb783feae33361c8f4c992fb65584d65913512b399a12130fdb39eb

Tx prefix hash: ce9318b190b2a516ab2646d1b55b7ad262c30e366e176e94ac51745158f2d707
Tx public key: 00b53f0cebcffde9246e5e5babd1e927feb7cdb1ceea6c31f9b850b3b3b7b885
Timestamp: 1746398535 Timestamp [UCT]: 2025-05-04 22:42:15 Age [y:d:h:m:s]: 00:195:03:45:55
Block: 1275888 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137191 RingCT/type: yes/0
Extra: 0100b53f0cebcffde9246e5e5babd1e927feb7cdb1ceea6c31f9b850b3b3b7b8850211000000031f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 829f649eb86d30a77c24495af81cae072c2bb76fea769b89b9a689fecc71f1ad 0.600000000000 1763203 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": 1275898, "vin": [ { "gen": { "height": 1275888 } } ], "vout": [ { "amount": 600000000, "target": { "key": "829f649eb86d30a77c24495af81cae072c2bb76fea769b89b9a689fecc71f1ad" } } ], "extra": [ 1, 0, 181, 63, 12, 235, 207, 253, 233, 36, 110, 94, 91, 171, 209, 233, 39, 254, 183, 205, 177, 206, 234, 108, 49, 249, 184, 80, 179, 179, 183, 184, 133, 2, 17, 0, 0, 0, 3, 31, 144, 81, 122, 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