Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26c8f335abb0068d51b2361c877b7b41917ed90592bd4de7e9f7bdbfdb7ae95c

Tx prefix hash: dad85be19192a01f534bced48d27d694bf038a1160d06e77b99df42b2c219724
Tx public key: 538e16de0e23d153c3d1dce7acba2f5e86534b78450544744ffe7782a3e8ce2c
Timestamp: 1577813224 Timestamp [UCT]: 2019-12-31 17:27:04 Age [y:d:h:m:s]: 04:364:23:39:50
Block: 35911 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1149954 RingCT/type: yes/0
Extra: 01538e16de0e23d153c3d1dce7acba2f5e86534b78450544744ffe7782a3e8ce2c021100000060feadaf7f000000000000000000

1 output(s) for total of 466.673137913000 dcy

stealth address amount amount idx
00: 8939e833e776e6df11d9a72295a91f9b0aa051761ac827ee169482644d079e71 466.673137913000 60651 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": 35921, "vin": [ { "gen": { "height": 35911 } } ], "vout": [ { "amount": 466673137913, "target": { "key": "8939e833e776e6df11d9a72295a91f9b0aa051761ac827ee169482644d079e71" } } ], "extra": [ 1, 83, 142, 22, 222, 14, 35, 209, 83, 195, 209, 220, 231, 172, 186, 47, 94, 134, 83, 75, 120, 69, 5, 68, 116, 79, 254, 119, 130, 163, 232, 206, 44, 2, 17, 0, 0, 0, 96, 254, 173, 175, 127, 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