Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 563eb61ab7f716cdfd0692c36e425a6ce83d1c3a6639d7566d4701903f55fb99

Tx prefix hash: f66b1ec93a216896fb19473e39f1b744bb03ce85572be85a64c834b085de6ccc
Tx public key: 6b43e19744eaa3cb1e8e5798cddb7a2b2647f42959978f670fd21bdf3ce34986
Timestamp: 1726339138 Timestamp [UCT]: 2024-09-14 18:38:58 Age [y:d:h:m:s]: 00:161:16:36:55
Block: 1110107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115351 RingCT/type: yes/0
Extra: 016b43e19744eaa3cb1e8e5798cddb7a2b2647f42959978f670fd21bdf3ce34986021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8303abcb7f37c837568b26bacc3aa2485d7587064ad47a3d5393c0b6a7abfc48 0.600000000000 1588596 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": 1110117, "vin": [ { "gen": { "height": 1110107 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8303abcb7f37c837568b26bacc3aa2485d7587064ad47a3d5393c0b6a7abfc48" } } ], "extra": [ 1, 107, 67, 225, 151, 68, 234, 163, 203, 30, 142, 87, 152, 205, 219, 122, 43, 38, 71, 244, 41, 89, 151, 143, 103, 15, 210, 27, 223, 60, 227, 73, 134, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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