Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7193fe4bb5812199139458d41cfb9591af62c8d7b90c01390806be0c223db79e

Tx prefix hash: bdc99a9caf98c2985add963fae0e17ec25c30437c2fa338b17fe458fa09133c9
Tx public key: 7efd6d63b2eeba6647556393f41bc874845f0f01cfd9e4888ed50947040e5e66
Timestamp: 1687392329 Timestamp [UCT]: 2023-06-22 00:05:29 Age [y:d:h:m:s]: 01:199:05:00:10
Block: 787468 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 403775 RingCT/type: yes/0
Extra: 017efd6d63b2eeba6647556393f41bc874845f0f01cfd9e4888ed50947040e5e6602110000000175e3f0e9000000000000000000

1 output(s) for total of 1.509356296000 dcy

stealth address amount amount idx
00: 8a09f6a0d6f7d10999f401dc544c331cf4d877bf6a1b46d55f5938dc292c9af2 1.509356296000 1237525 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": 787478, "vin": [ { "gen": { "height": 787468 } } ], "vout": [ { "amount": 1509356296, "target": { "key": "8a09f6a0d6f7d10999f401dc544c331cf4d877bf6a1b46d55f5938dc292c9af2" } } ], "extra": [ 1, 126, 253, 109, 99, 178, 238, 186, 102, 71, 85, 99, 147, 244, 27, 200, 116, 132, 95, 15, 1, 207, 217, 228, 136, 142, 213, 9, 71, 4, 14, 94, 102, 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