Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a3ca65d5cec730cca343c78f8132050bb53ef86552421687579b9f8936e203d

Tx prefix hash: baa2ccae8fd245410321d6a27b583556e48221da520d8e38c80eeef34607b174
Tx public key: 35600083d97da30f90b83c6e7be00ca4c82b36e80309f9af69ec5e5fb3e7d38e
Timestamp: 1708229487 Timestamp [UCT]: 2024-02-18 04:11:27 Age [y:d:h:m:s]: 01:045:19:10:38
Block: 959966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293763 RingCT/type: yes/0
Extra: 0135600083d97da30f90b83c6e7be00ca4c82b36e80309f9af69ec5e5fb3e7d38e02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 20063179ac2caaac4dfa6e09c385b7e844b1d31e7b23f9f65bfe36b182e1b01a 0.600000000000 1419525 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": 959976, "vin": [ { "gen": { "height": 959966 } } ], "vout": [ { "amount": 600000000, "target": { "key": "20063179ac2caaac4dfa6e09c385b7e844b1d31e7b23f9f65bfe36b182e1b01a" } } ], "extra": [ 1, 53, 96, 0, 131, 217, 125, 163, 15, 144, 184, 60, 110, 123, 224, 12, 164, 200, 43, 54, 232, 3, 9, 249, 175, 105, 236, 94, 95, 179, 231, 211, 142, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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