Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 999a9c2dea72f43526765ec27622ccc390145d97c91dc876b45d069c386e23f0

Tx prefix hash: 24639f04a87d18d0bcc5c6d88902b0a9bf51ebe99f3a3bcbe6f739f549e770a6
Tx public key: e9f61383f9b4736e1b7d88c1422d097de21effbf7a234084b6c7015e8bed6d3b
Timestamp: 1727416353 Timestamp [UCT]: 2024-09-27 05:52:33 Age [y:d:h:m:s]: 00:263:06:23:36
Block: 1119052 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187898 RingCT/type: yes/0
Extra: 01e9f61383f9b4736e1b7d88c1422d097de21effbf7a234084b6c7015e8bed6d3b021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89005ecce2d86d40bc6f7efbe1254beccf90ec19d6e5e44b1a07e580fdda86aa 0.600000000000 1600461 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": 1119062, "vin": [ { "gen": { "height": 1119052 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89005ecce2d86d40bc6f7efbe1254beccf90ec19d6e5e44b1a07e580fdda86aa" } } ], "extra": [ 1, 233, 246, 19, 131, 249, 180, 115, 110, 27, 125, 136, 193, 66, 45, 9, 125, 226, 30, 255, 191, 122, 35, 64, 132, 182, 199, 1, 94, 139, 237, 109, 59, 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