Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a02cbfe8d1ee5b69c5a52650de31c13f647edcef19f963ac094ba729a573238

Tx prefix hash: e9855c9e4ba22e594de99742c30a571f6c62f873e78bedc017fe1d9e6a1edd23
Tx public key: 8729b5eec4e07cc83ce3546b4fb469b297f8f9c7bf8cdb36f68bb598ecbb5a61
Timestamp: 1705126072 Timestamp [UCT]: 2024-01-13 06:07:52 Age [y:d:h:m:s]: 00:354:07:07:36
Block: 934219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253683 RingCT/type: yes/0
Extra: 018729b5eec4e07cc83ce3546b4fb469b297f8f9c7bf8cdb36f68bb598ecbb5a6102110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6cf2ffb7aabde1a2b2606abf21f8a7de3b47a369660baa2d57d772545124d75 0.600000000000 1392207 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": 934229, "vin": [ { "gen": { "height": 934219 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6cf2ffb7aabde1a2b2606abf21f8a7de3b47a369660baa2d57d772545124d75" } } ], "extra": [ 1, 135, 41, 181, 238, 196, 224, 124, 200, 60, 227, 84, 107, 79, 180, 105, 178, 151, 248, 249, 199, 191, 140, 219, 54, 246, 139, 181, 152, 236, 187, 90, 97, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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