Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9afa03860a33b29134ccc17ee2e8d553f59048b3dff9cbeefad862ed20e7e740

Tx prefix hash: 9925d99f859ae0ce42e9dac9bf74f5c4d62da571857d97f081e7a66255d37589
Tx public key: 59f0a03339e449bf6320d0b2bb22acf80151c50e57df8a2aa991f60a84722307
Timestamp: 1709249924 Timestamp [UCT]: 2024-02-29 23:38:44 Age [y:d:h:m:s]: 01:255:05:32:52
Block: 968443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 441125 RingCT/type: yes/0
Extra: 0159f0a03339e449bf6320d0b2bb22acf80151c50e57df8a2aa991f60a8472230702110000000149a185bb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a87378c89b959aea0630dc46ae4c886cfb7a772f071bfc3908b816a246a490a5 0.600000000000 1428258 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": 968453, "vin": [ { "gen": { "height": 968443 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a87378c89b959aea0630dc46ae4c886cfb7a772f071bfc3908b816a246a490a5" } } ], "extra": [ 1, 89, 240, 160, 51, 57, 228, 73, 191, 99, 32, 208, 178, 187, 34, 172, 248, 1, 81, 197, 14, 87, 223, 138, 42, 169, 145, 246, 10, 132, 114, 35, 7, 2, 17, 0, 0, 0, 1, 73, 161, 133, 187, 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