Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d881741696016b38554fdfac5e6b774e3d7ddaa2a20d96339a6a0f5f9ac4a48

Tx prefix hash: 68ee9b2889a072fdc37b6732bc5a8bb64690e5ce1d9e24905a75c7a6c3024d6f
Tx public key: 7e2df63f459f4fd49bd13eb91385d2dfd0e6db95842922a5ff41ff5aeb7501f4
Timestamp: 1699291471 Timestamp [UCT]: 2023-11-06 17:24:31 Age [y:d:h:m:s]: 01:109:20:57:16
Block: 885873 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339676 RingCT/type: yes/0
Extra: 017e2df63f459f4fd49bd13eb91385d2dfd0e6db95842922a5ff41ff5aeb7501f402110000000175e3f0e9000000000000000000

1 output(s) for total of 0.712418210000 dcy

stealth address amount amount idx
00: 4da771d5feb7e3776c2a744dc68c436b6b33d18515bac40c3678364d7890c745 0.712418210000 1341666 of 0

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": 885883, "vin": [ { "gen": { "height": 885873 } } ], "vout": [ { "amount": 712418210, "target": { "key": "4da771d5feb7e3776c2a744dc68c436b6b33d18515bac40c3678364d7890c745" } } ], "extra": [ 1, 126, 45, 246, 63, 69, 159, 79, 212, 155, 209, 62, 185, 19, 133, 210, 223, 208, 230, 219, 149, 132, 41, 34, 165, 255, 65, 255, 90, 235, 117, 1, 244, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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