Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62b1375d04d1d1868b9e42b44b6c56d0d5490a87fb37397e19b3dd8fa0f08c6a

Tx prefix hash: ee7df8d21b4a67f1dd7bbca45a09cc9126b3ba878a6a7e9a7aaccd7bb328d16e
Tx public key: 2b0c87e3c89ec080d486ebbaf6c00d859097e952b522930d4e25ee9f6c9fa6d3
Timestamp: 1710672845 Timestamp [UCT]: 2024-03-17 10:54:05 Age [y:d:h:m:s]: 01:040:20:57:21
Block: 980246 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290195 RingCT/type: yes/0
Extra: 012b0c87e3c89ec080d486ebbaf6c00d859097e952b522930d4e25ee9f6c9fa6d302110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79c76853fd1f21e46c2f72a7bad51672194c52c65642826bf54357be4c9b3241 0.600000000000 1440311 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": 980256, "vin": [ { "gen": { "height": 980246 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79c76853fd1f21e46c2f72a7bad51672194c52c65642826bf54357be4c9b3241" } } ], "extra": [ 1, 43, 12, 135, 227, 200, 158, 192, 128, 212, 134, 235, 186, 246, 192, 13, 133, 144, 151, 233, 82, 181, 34, 147, 13, 78, 37, 238, 159, 108, 159, 166, 211, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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