Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a066bd0c2a3fd293171a01395688825d8afbef324efd2c04e54de974a5cd368f

Tx prefix hash: 93b1379c3932c9f2a043bf32b2d274450ffca04836308e486baed03dfbcfc675
Tx public key: 8f3bfeb51b4110f05a1372851d8e7b71c6a022420d8ff11b67f42cc3f21d5f45
Timestamp: 1763471536 Timestamp [UCT]: 2025-11-18 13:12:16 Age [y:d:h:m:s]: 00:009:20:14:42
Block: 1414823 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7056 RingCT/type: yes/0
Extra: 018f3bfeb51b4110f05a1372851d8e7b71c6a022420d8ff11b67f42cc3f21d5f45021100000002fb8fd089000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96946b7989358e32ee079e3d81c00f37145b71443c9ea72bdbc60576f9a0a775 0.600000000000 1903316 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": 1414833, "vin": [ { "gen": { "height": 1414823 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96946b7989358e32ee079e3d81c00f37145b71443c9ea72bdbc60576f9a0a775" } } ], "extra": [ 1, 143, 59, 254, 181, 27, 65, 16, 240, 90, 19, 114, 133, 29, 142, 123, 113, 198, 160, 34, 66, 13, 143, 241, 27, 103, 244, 44, 195, 242, 29, 95, 69, 2, 17, 0, 0, 0, 2, 251, 143, 208, 137, 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