Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f943ee82af66fd6388f6ecf5f21b60d25c4ff641e8084ec02d4ca64ea6e7853

Tx prefix hash: a7f9839755dae14c0cb72ec9991a8dc5dae1ce1c76a80b4d198e65be702bb87b
Tx public key: 83a23604e3e9204ddef68f6bee8b1e57ff9b34cc7502a56209c1fea4dde38451
Timestamp: 1719489564 Timestamp [UCT]: 2024-06-27 11:59:24 Age [y:d:h:m:s]: 00:282:21:47:43
Block: 1053320 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202158 RingCT/type: yes/0
Extra: 0183a23604e3e9204ddef68f6bee8b1e57ff9b34cc7502a56209c1fea4dde384510211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c90d5e0100cfa1a2403eebdc9cf8896c87247ed14f4c2098716e995980cd30d5 0.600000000000 1523667 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": 1053330, "vin": [ { "gen": { "height": 1053320 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c90d5e0100cfa1a2403eebdc9cf8896c87247ed14f4c2098716e995980cd30d5" } } ], "extra": [ 1, 131, 162, 54, 4, 227, 233, 32, 77, 222, 246, 143, 107, 238, 139, 30, 87, 255, 155, 52, 204, 117, 2, 165, 98, 9, 193, 254, 164, 221, 227, 132, 81, 2, 17, 0, 0, 0, 1, 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