Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a28ffaa300d9f9816c6e54c3f46800ffa2bb7ca0b2ec6d88f1d56ebcd5de4ee

Tx prefix hash: 396dcdf020df01911376d0296486fb25fd3a555c67329154739dfe088a185424
Tx public key: 77f8adf042fbdd86c0791d68aa23e6108fc9797d485359b146ecd35fc1f1ae29
Timestamp: 1703358413 Timestamp [UCT]: 2023-12-23 19:06:53 Age [y:d:h:m:s]: 01:333:19:15:41
Block: 919587 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497415 RingCT/type: yes/0
Extra: 0177f8adf042fbdd86c0791d68aa23e6108fc9797d485359b146ecd35fc1f1ae2902110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7bd2199b1aa14c4a1afab721ac4b3aec7252ad8e8a99057fb59814de17f5d0c 0.600000000000 1377261 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": 919597, "vin": [ { "gen": { "height": 919587 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7bd2199b1aa14c4a1afab721ac4b3aec7252ad8e8a99057fb59814de17f5d0c" } } ], "extra": [ 1, 119, 248, 173, 240, 66, 251, 221, 134, 192, 121, 29, 104, 170, 35, 230, 16, 143, 201, 121, 125, 72, 83, 89, 177, 70, 236, 211, 95, 193, 241, 174, 41, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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