Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ecc7b7e370e70e696165a1d812bc91e3697f75cb30f1ce270973d8fea8c79beb

Tx prefix hash: c7c3d2f6b2416eba0eb1eaba53d9df830e1f00e5d3b4219864172009dc38cbc0
Tx public key: 4ce21e417af41c7dfcfbed819da445bf3ea17b16413bbb58a2295765ebbe851f
Timestamp: 1706351064 Timestamp [UCT]: 2024-01-27 10:24:24 Age [y:d:h:m:s]: 01:284:15:19:05
Block: 944376 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 462226 RingCT/type: yes/0
Extra: 014ce21e417af41c7dfcfbed819da445bf3ea17b16413bbb58a2295765ebbe851f0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 862a2fe668dcc7ac418ff13f456b330dd58f3bf3a2bcca9afc72e84d59eca504 0.600000000000 1402612 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": 944386, "vin": [ { "gen": { "height": 944376 } } ], "vout": [ { "amount": 600000000, "target": { "key": "862a2fe668dcc7ac418ff13f456b330dd58f3bf3a2bcca9afc72e84d59eca504" } } ], "extra": [ 1, 76, 226, 30, 65, 122, 244, 28, 125, 252, 251, 237, 129, 157, 164, 69, 191, 62, 161, 123, 22, 65, 59, 187, 88, 162, 41, 87, 101, 235, 190, 133, 31, 2, 17, 0, 0, 0, 5, 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