Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba0c41483b99e9e5a86fea5e0238ef65ef40b926ab17a13fe325309af750340b

Tx prefix hash: e2dc3e9cf0c6e09c510b0c3aef6d760e4f4923aa8584bf5eb67ff520b69c701e
Tx public key: 9cb92b13cf919e6a53ebf09732dd31ffa9d90910874cc0a5d4503ca79c0db99b
Timestamp: 1724869084 Timestamp [UCT]: 2024-08-28 18:18:04 Age [y:d:h:m:s]: 00:173:07:16:12
Block: 1097917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123666 RingCT/type: yes/0
Extra: 019cb92b13cf919e6a53ebf09732dd31ffa9d90910874cc0a5d4503ca79c0db99b02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3db4dfdb07c740d9c25414da0b734e0c66219fa61323aa15357c3af34561efc5 0.600000000000 1573454 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": 1097927, "vin": [ { "gen": { "height": 1097917 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3db4dfdb07c740d9c25414da0b734e0c66219fa61323aa15357c3af34561efc5" } } ], "extra": [ 1, 156, 185, 43, 19, 207, 145, 158, 106, 83, 235, 240, 151, 50, 221, 49, 255, 169, 217, 9, 16, 135, 76, 192, 165, 212, 80, 60, 167, 156, 13, 185, 155, 2, 17, 0, 0, 0, 4, 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