Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 312e071d975c137cf726c8ecbca4b59f6d812963e47f71c6aca296dc24a10ab1

Tx prefix hash: cc8ec79adb3eb7a16ea8a5c8260d61587a9c2a1a76c1a5cc5fe1ca50b8eee764
Tx public key: aace2f79afb2df8975a5859eb51bded9dc5df961ebaaa344ec004ec26ad6e42e
Timestamp: 1756671996 Timestamp [UTC]: 2025-08-31 20:26:36 Age [y:d:h:m:s]: 01:079:08:09:45
Block: 1358594 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323042 RingCT/type: yes/0
Extra: 01aace2f79afb2df8975a5859eb51bded9dc5df961ebaaa344ec004ec26ad6e42e021100000004ad7948d0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4c628a3e4db590f5148d28d3b524a4b174ed7b6c049143c94ee758c29532255a 0.000600000000 1846607 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": 1358604, "vin": [ { "gen": { "height": 1358594 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c628a3e4db590f5148d28d3b524a4b174ed7b6c049143c94ee758c29532255a" } } ], "extra": [ 1, 170, 206, 47, 121, 175, 178, 223, 137, 117, 165, 133, 158, 181, 27, 222, 217, 220, 93, 249, 97, 235, 170, 163, 68, 236, 0, 78, 194, 106, 214, 228, 46, 2, 17, 0, 0, 0, 4, 173, 121, 72, 208, 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: