Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20bc3ebebbc0d9522e2d204ccf7e2417e5cf4e59cb3108464e48bd3ba5c2d9f8

Tx prefix hash: 635776a179886f083a3decb31ebeb5c127e055753ed300de0501364e8ac6ceec
Tx public key: 6f512728a07c326d8ea12530b673632524e320f81d058c5bcee542f46cb8cae7
Timestamp: 1709214314 Timestamp [UCT]: 2024-02-29 13:45:14 Age [y:d:h:m:s]: 01:037:01:26:47
Block: 968141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287481 RingCT/type: yes/0
Extra: 016f512728a07c326d8ea12530b673632524e320f81d058c5bcee542f46cb8cae70211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3915c6a27a1c642f00e67345f6b9a3095d140c3aa04da0444d9c4beef3c5ee46 0.600000000000 1427940 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": 968151, "vin": [ { "gen": { "height": 968141 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3915c6a27a1c642f00e67345f6b9a3095d140c3aa04da0444d9c4beef3c5ee46" } } ], "extra": [ 1, 111, 81, 39, 40, 160, 124, 50, 109, 142, 161, 37, 48, 182, 115, 99, 37, 36, 227, 32, 248, 29, 5, 140, 91, 206, 229, 66, 244, 108, 184, 202, 231, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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