Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97933697bccbe32ff21595563afdd4c1bc387dbc710b29f6d35f79859a77f41b

Tx prefix hash: 3e6552adc56796f464df36cec06f6089583d18f2b9730d61008e0f21d41d5c3f
Tx public key: 98e3d0fde7dcf4aad3e4a9055606c031abbee76c5d77d703519176ecc914d7d6
Timestamp: 1715125069 Timestamp [UCT]: 2024-05-07 23:37:49 Age [y:d:h:m:s]: 00:333:08:31:14
Block: 1017141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238290 RingCT/type: yes/0
Extra: 0198e3d0fde7dcf4aad3e4a9055606c031abbee76c5d77d703519176ecc914d7d60211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c069b12d7d517284243ca7d0816ca54ad85596c8e5c45ba73d50b22064b88f01 0.600000000000 1480908 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": 1017151, "vin": [ { "gen": { "height": 1017141 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c069b12d7d517284243ca7d0816ca54ad85596c8e5c45ba73d50b22064b88f01" } } ], "extra": [ 1, 152, 227, 208, 253, 231, 220, 244, 170, 211, 228, 169, 5, 86, 6, 192, 49, 171, 190, 231, 108, 93, 119, 215, 3, 81, 145, 118, 236, 201, 20, 215, 214, 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