Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 959d685fadae0afe8fb3d431e0bbdce8deec173187f513fe6df5ffe17c709149

Tx prefix hash: bdcee1ac06d21c1a02a1b674f9c16ac20ce492a134542334a9f0700c1aa7cb42
Tx public key: 000de39ce09cca8de3bbc77b48c31f032e9d038bd3ba1372f6b66c9883b4893a
Timestamp: 1741971230 Timestamp [UTC]: 2025-03-14 16:53:50 Age [y:d:h:m:s]: 01:252:20:05:41
Block: 1239254 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 444240 RingCT/type: yes/0
Extra: 01000de39ce09cca8de3bbc77b48c31f032e9d038bd3ba1372f6b66c9883b4893a021100000009007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4b3794a8d2a7d35ac92124fe79050e3f2887c612c16382f5392174680353c3f9 0.000600000000 1726219 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 dinastycoin-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": 1239264, "vin": [ { "gen": { "height": 1239254 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b3794a8d2a7d35ac92124fe79050e3f2887c612c16382f5392174680353c3f9" } } ], "extra": [ 1, 0, 13, 227, 156, 224, 156, 202, 141, 227, 187, 199, 123, 72, 195, 31, 3, 46, 157, 3, 139, 211, 186, 19, 114, 246, 182, 108, 152, 131, 180, 137, 58, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: