Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5c93133cb675f4c98df202336e27be628549f4c5673078ec0cd94164a408c93

Tx prefix hash: d41a22ced1cb262af65b3cb26f4c29fc3e1e3065aad0ba3922a083a9eae959f1
Tx public key: b98abf90dc25b9c98bd06fe71cd4962aea48311305f5589e26ae8127938c4aa6
Timestamp: 1581124592 Timestamp [UCT]: 2020-02-08 01:16:32 Age [y:d:h:m:s]: 05:117:02:59:48
Block: 60796 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1236007 RingCT/type: yes/0
Extra: 01b98abf90dc25b9c98bd06fe71cd4962aea48311305f5589e26ae8127938c4aa60211000000248a2ee0d9000000000000000000

1 output(s) for total of 385.974338480000 dcy

stealth address amount amount idx
00: 373425cb1102ad36784ac02cb2a88c5ed680649e906821aada2759dc002a62be 385.974338480000 111983 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": 60806, "vin": [ { "gen": { "height": 60796 } } ], "vout": [ { "amount": 385974338480, "target": { "key": "373425cb1102ad36784ac02cb2a88c5ed680649e906821aada2759dc002a62be" } } ], "extra": [ 1, 185, 138, 191, 144, 220, 37, 185, 201, 139, 208, 111, 231, 28, 212, 150, 42, 234, 72, 49, 19, 5, 245, 88, 158, 38, 174, 129, 39, 147, 140, 74, 166, 2, 17, 0, 0, 0, 36, 138, 46, 224, 217, 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