Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0517db84b437333d7051a758db2584b16b911281d572e37229343e44b3cf39ad

Tx prefix hash: daf1ba7aa8a3b610cba2c07185502862a08e1dd43fc133be634bad9c87795422
Tx public key: 64fd13f4b8a6402064d4d24a2443938244a1f532680e0a9ff8d94c56e76b71e1
Timestamp: 1724062775 Timestamp [UCT]: 2024-08-19 10:19:35 Age [y:d:h:m:s]: 00:241:23:49:16
Block: 1091240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172832 RingCT/type: yes/0
Extra: 0164fd13f4b8a6402064d4d24a2443938244a1f532680e0a9ff8d94c56e76b71e102110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38e391e5f82a3f162b2c9d54bba3bcf7d744c3647a4eb666e73627a52f164cc2 0.600000000000 1565871 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": 1091250, "vin": [ { "gen": { "height": 1091240 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38e391e5f82a3f162b2c9d54bba3bcf7d744c3647a4eb666e73627a52f164cc2" } } ], "extra": [ 1, 100, 253, 19, 244, 184, 166, 64, 32, 100, 212, 210, 74, 36, 67, 147, 130, 68, 161, 245, 50, 104, 14, 10, 159, 248, 217, 76, 86, 231, 107, 113, 225, 2, 17, 0, 0, 0, 3, 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