Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9935a612a8863a0911630fcaca2a7a9d7becf2b7fb16b39b317c97c783766e3a

Tx prefix hash: 9f19434311bfb32d72904abc81fbe68f53f0efdcba90fc11e66dd4cc8fce4888
Tx public key: ddd41646e4daf3506c053dc596b4780c682dab30a21e6cb4b563925f2ff7ad4b
Timestamp: 1711351680 Timestamp [UCT]: 2024-03-25 07:28:00 Age [y:d:h:m:s]: 00:251:03:00:25
Block: 985882 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179768 RingCT/type: yes/0
Extra: 01ddd41646e4daf3506c053dc596b4780c682dab30a21e6cb4b563925f2ff7ad4b0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf55e81868905354ed01034cf6b56011ebc9e560e4baaab70ae9dbcb05b7a50b 0.600000000000 1446103 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": 985892, "vin": [ { "gen": { "height": 985882 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf55e81868905354ed01034cf6b56011ebc9e560e4baaab70ae9dbcb05b7a50b" } } ], "extra": [ 1, 221, 212, 22, 70, 228, 218, 243, 80, 108, 5, 61, 197, 150, 180, 120, 12, 104, 45, 171, 48, 162, 30, 108, 180, 181, 99, 146, 95, 47, 247, 173, 75, 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