Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2573b08365c01b4a10637df4d15c942a1af1a667cd39bbc069a1ac3d31f87845

Tx prefix hash: d01e6509abbbf467337df7cd0d3a320c4e305227075f34c1f63b888bb35a368c
Tx public key: a715c7ad79d7ffeb0c965528d7e3e57af0f34cb2dc3d0823a11ced4e6ab13331
Timestamp: 1703460897 Timestamp [UCT]: 2023-12-24 23:34:57 Age [y:d:h:m:s]: 01:098:11:12:29
Block: 920445 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331473 RingCT/type: yes/0
Extra: 01a715c7ad79d7ffeb0c965528d7e3e57af0f34cb2dc3d0823a11ced4e6ab1333102110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f365f917dd11e461e99872acda638dee7f0b3223f1d62cc07194efd8b1b91379 0.600000000000 1378123 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": 920455, "vin": [ { "gen": { "height": 920445 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f365f917dd11e461e99872acda638dee7f0b3223f1d62cc07194efd8b1b91379" } } ], "extra": [ 1, 167, 21, 199, 173, 121, 215, 255, 235, 12, 150, 85, 40, 215, 227, 229, 122, 240, 243, 76, 178, 220, 61, 8, 35, 161, 28, 237, 78, 106, 177, 51, 49, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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