Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f52fc040bc0a87e52c9d9d3eb13bd731366124f5fb81c7a5765f17075837409a

Tx prefix hash: a8438e2134c31bb6f86ab205d7ecbe9590604b2e3f327c3abc2e387fcfac7b16
Tx public key: d93839150dcb608fa2218f0dafc4adc9e7da5ec9ffc7f8c19b366e502d0a5622
Timestamp: 1722049576 Timestamp [UCT]: 2024-07-27 03:06:16 Age [y:d:h:m:s]: 00:293:23:26:34
Block: 1074543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210044 RingCT/type: yes/0
Extra: 01d93839150dcb608fa2218f0dafc4adc9e7da5ec9ffc7f8c19b366e502d0a562202110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f1863baeff49aa4d9365d0406913afb3296e761d90e912265ae32cca003e88f 0.600000000000 1547056 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": 1074553, "vin": [ { "gen": { "height": 1074543 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f1863baeff49aa4d9365d0406913afb3296e761d90e912265ae32cca003e88f" } } ], "extra": [ 1, 217, 56, 57, 21, 13, 203, 96, 143, 162, 33, 143, 13, 175, 196, 173, 201, 231, 218, 94, 201, 255, 199, 248, 193, 155, 54, 110, 80, 45, 10, 86, 34, 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