Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc96678e3107967a055372a43c7a670c6300b527adc4e650b502fd75a8221302

Tx prefix hash: 5fb124c8b886165fad9477d54d9823216bd08fb0854e98bc2ef3fb45e1fc4cb6
Tx public key: 414a8aaafd666dcfa764550beb84618228ff1f0fb56608c4a6ff34af4296f73f
Timestamp: 1710335723 Timestamp [UCT]: 2024-03-13 13:15:23 Age [y:d:h:m:s]: 01:015:19:15:14
Block: 977460 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272253 RingCT/type: yes/0
Extra: 01414a8aaafd666dcfa764550beb84618228ff1f0fb56608c4a6ff34af4296f73f0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6725566f339594b23b5afff7c2156b9d8fee4dae8796d9b03b534e7f4fe3c5a 0.600000000000 1437463 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": 977470, "vin": [ { "gen": { "height": 977460 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6725566f339594b23b5afff7c2156b9d8fee4dae8796d9b03b534e7f4fe3c5a" } } ], "extra": [ 1, 65, 74, 138, 170, 253, 102, 109, 207, 167, 100, 85, 11, 235, 132, 97, 130, 40, 255, 31, 15, 181, 102, 8, 196, 166, 255, 52, 175, 66, 150, 247, 63, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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