Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92f9c110a088e14c23b221de92ec6b9b287a89a30e7c90a60ee82b3362a7789a

Tx prefix hash: 53cbb3a21936b42abe28d8e244f4dc159506c2b41abf6df056c2506fc79960ca
Tx public key: 26786bfe5d8ee900956fd1554f1e49d777a5b9d6e225493963984168010da42f
Timestamp: 1649580337 Timestamp [UCT]: 2022-04-10 08:45:37 Age [y:d:h:m:s]: 02:339:14:47:36
Block: 477161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 762289 RingCT/type: yes/0
Extra: 0126786bfe5d8ee900956fd1554f1e49d777a5b9d6e225493963984168010da42f021100000009bf7ee4e7000000000000000000

1 output(s) for total of 16.105260988000 dcy

stealth address amount amount idx
00: 16516f665eb036d01373579a7b2e81dc6e60f25e1a0a161b0214ab916c1695c7 16.105260988000 897790 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": 477171, "vin": [ { "gen": { "height": 477161 } } ], "vout": [ { "amount": 16105260988, "target": { "key": "16516f665eb036d01373579a7b2e81dc6e60f25e1a0a161b0214ab916c1695c7" } } ], "extra": [ 1, 38, 120, 107, 254, 93, 142, 233, 0, 149, 111, 209, 85, 79, 30, 73, 215, 119, 165, 185, 214, 226, 37, 73, 57, 99, 152, 65, 104, 1, 13, 164, 47, 2, 17, 0, 0, 0, 9, 191, 126, 228, 231, 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