Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8320a746e105f00de8159a8fb530e20d50b5626ff4a2e2a28e0c9a323cbd98cf

Tx prefix hash: 610d6e58fc7f2ee51b1ee0ead5e4bb612f1b7062e3ea86df70dbbf69e409177d
Tx public key: a0eeb52f18e9dde23fb8b84dd9c89a6db26a067212cd0cf2275e05aa9ef0dbb4
Timestamp: 1592761342 Timestamp [UCT]: 2020-06-21 17:42:22 Age [y:d:h:m:s]: 04:255:20:40:54
Block: 110207 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1121084 RingCT/type: yes/0
Extra: 01a0eeb52f18e9dde23fb8b84dd9c89a6db26a067212cd0cf2275e05aa9ef0dbb402110000005046a11e8a000000000000000000

1 output(s) for total of 264.751974445000 dcy

stealth address amount amount idx
00: a5ee855b4e3f72dfeb2ec172e7939756e14f810f3440196c6d5caeef264285be 264.751974445000 190845 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": 110217, "vin": [ { "gen": { "height": 110207 } } ], "vout": [ { "amount": 264751974445, "target": { "key": "a5ee855b4e3f72dfeb2ec172e7939756e14f810f3440196c6d5caeef264285be" } } ], "extra": [ 1, 160, 238, 181, 47, 24, 233, 221, 226, 63, 184, 184, 77, 217, 200, 154, 109, 178, 106, 6, 114, 18, 205, 12, 242, 39, 94, 5, 170, 158, 240, 219, 180, 2, 17, 0, 0, 0, 80, 70, 161, 30, 138, 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