Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88f7ad02ae816419738f6c378d549aa0de164c4fd5b703a6af4b6f4b2a80e8cb

Tx prefix hash: d869b185e59e73d45cdf3bea2737df0479fdf7d2759cf31b4b10dcd3da9e1a9e
Tx public key: 6903eb51a5470c990c21c073c245a250848683b1ff0c8f9b2d0052862895683c
Timestamp: 1721309211 Timestamp [UCT]: 2024-07-18 13:26:51 Age [y:d:h:m:s]: 00:300:06:22:17
Block: 1068430 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214533 RingCT/type: yes/0
Extra: 016903eb51a5470c990c21c073c245a250848683b1ff0c8f9b2d0052862895683c02110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf925f6c7e748423cfc108cffb58fad79cfdbac9ac461d01bddca410047524bc 0.600000000000 1539507 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": 1068440, "vin": [ { "gen": { "height": 1068430 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf925f6c7e748423cfc108cffb58fad79cfdbac9ac461d01bddca410047524bc" } } ], "extra": [ 1, 105, 3, 235, 81, 165, 71, 12, 153, 12, 33, 192, 115, 194, 69, 162, 80, 132, 134, 131, 177, 255, 12, 143, 155, 45, 0, 82, 134, 40, 149, 104, 60, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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