Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1e87750a756187daca0b2112debd1d0aeac99ce23784cfd6e099401fd283c44

Tx prefix hash: c8de1339c036086bf53b8d336f0d19a9c76f3dd6287f6a944fd4ca69fbf029be
Tx public key: 84cfae7b6a890b77eecbac0c52fcadd058c82850581bfcc93c3e88d2a50dd0bc
Timestamp: 1714276216 Timestamp [UCT]: 2024-04-28 03:50:16 Age [y:d:h:m:s]: 01:183:01:18:05
Block: 1010100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389461 RingCT/type: yes/0
Extra: 0184cfae7b6a890b77eecbac0c52fcadd058c82850581bfcc93c3e88d2a50dd0bc02110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6b8c4e882b19a00c808236f4323a47be49781782da07d059df5b83aec889890 0.600000000000 1471956 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": 1010110, "vin": [ { "gen": { "height": 1010100 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6b8c4e882b19a00c808236f4323a47be49781782da07d059df5b83aec889890" } } ], "extra": [ 1, 132, 207, 174, 123, 106, 137, 11, 119, 238, 203, 172, 12, 82, 252, 173, 208, 88, 200, 40, 80, 88, 27, 252, 201, 60, 62, 136, 210, 165, 13, 208, 188, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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