Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac01923f348d6ae28fe48b5aa163614c08df3181daf1b121ac02c94d3ecf42b2

Tx prefix hash: bf53e70e90e15264fbc0700de00806a14803f2c8fcfaa6bdcab5465e689a9745
Tx public key: eeec6ef9e51e276ce3663a0c858304600832abe4dac6fcfc383aaf41ea9c2b28
Timestamp: 1744386211 Timestamp [UTC]: 2025-04-11 15:43:31 Age [y:d:h:m:s]: 01:225:03:35:52
Block: 1259238 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 424912 RingCT/type: yes/0
Extra: 01eeec6ef9e51e276ce3663a0c858304600832abe4dac6fcfc383aaf41ea9c2b280211000000016c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a0a4f9948ba576097369ff46d6dd76f43adf3b645940652c02a04e964c5df517 0.000600000000 1746377 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": 1259248, "vin": [ { "gen": { "height": 1259238 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0a4f9948ba576097369ff46d6dd76f43adf3b645940652c02a04e964c5df517" } } ], "extra": [ 1, 238, 236, 110, 249, 229, 30, 39, 108, 227, 102, 58, 12, 133, 131, 4, 96, 8, 50, 171, 228, 218, 198, 252, 252, 56, 58, 175, 65, 234, 156, 43, 40, 2, 17, 0, 0, 0, 1, 108, 152, 170, 61, 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: