Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 151b53d63491c47a76da42ae86e7cec810654b095953935f917ee58fbc6a571f

Tx prefix hash: 02145dd4dbd1706be8aa936a016dd885052f28f28dea2bd514d69ffa380c0b50
Tx public key: 68e9ea07f8d8b597b7d0caf02416580b475c5bcbc985fa50baab81953a488706
Timestamp: 1581363669 Timestamp [UCT]: 2020-02-10 19:41:09 Age [y:d:h:m:s]: 05:092:11:41:55
Block: 62219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1218936 RingCT/type: yes/0
Extra: 0168e9ea07f8d8b597b7d0caf02416580b475c5bcbc985fa50baab81953a4887060211394e3f3400000000000000000000000000

1 output(s) for total of 381.806607300000 dcy

stealth address amount amount idx
00: 351e8de16d9e5d8adaa75b882b299740d5f0a2970539c1c64fea073594af25d6 381.806607300000 114742 of 0

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": 62229, "vin": [ { "gen": { "height": 62219 } } ], "vout": [ { "amount": 381806607300, "target": { "key": "351e8de16d9e5d8adaa75b882b299740d5f0a2970539c1c64fea073594af25d6" } } ], "extra": [ 1, 104, 233, 234, 7, 248, 216, 181, 151, 183, 208, 202, 240, 36, 22, 88, 11, 71, 92, 91, 203, 201, 133, 250, 80, 186, 171, 129, 149, 58, 72, 135, 6, 2, 17, 57, 78, 63, 52, 0, 0, 0, 0, 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