Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b1aa6af9e26e516508e003ba9f843d640743cb135c515b9a3ebe699eccc356d

Tx prefix hash: ab899a7501000181bc5c2a27ffe6bead2f241399466c7328c7c5d7ab22122b00
Tx public key: dbb2a9f4311a6fe6ce82acff487eb95fc781ab6514bb76325609df299dadd5b7
Timestamp: 1699347266 Timestamp [UCT]: 2023-11-07 08:54:26 Age [y:d:h:m:s]: 01:188:17:56:47
Block: 886337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396112 RingCT/type: yes/0
Extra: 01dbb2a9f4311a6fe6ce82acff487eb95fc781ab6514bb76325609df299dadd5b702110000000175e3f0e9000000000000000000

1 output(s) for total of 0.709900671000 dcy

stealth address amount amount idx
00: f20fe9ad598daf6a5eba646bdaa41d4a04e27e62737c103a6f1ea409b36f4611 0.709900671000 1342152 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": 886347, "vin": [ { "gen": { "height": 886337 } } ], "vout": [ { "amount": 709900671, "target": { "key": "f20fe9ad598daf6a5eba646bdaa41d4a04e27e62737c103a6f1ea409b36f4611" } } ], "extra": [ 1, 219, 178, 169, 244, 49, 26, 111, 230, 206, 130, 172, 255, 72, 126, 185, 95, 199, 129, 171, 101, 20, 187, 118, 50, 86, 9, 223, 41, 157, 173, 213, 183, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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