Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a797f631e47137e32f917f265c99bc64b626b985a714524ec4dc23012ee461a2

Tx prefix hash: 70207a6c49366016aea9db1dd4910e11dc9f7e64a66cb566cdd41ba09bb27ff7
Tx public key: 064e3e6b40b4966ca47d3c832d2d0640085415a0c992687d6a7cc7680daae4c7
Timestamp: 1757680706 Timestamp [UTC]: 2025-09-12 12:38:26 Age [y:d:h:m:s]: 00:245:10:05:47
Block: 1366835 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167855 RingCT/type: yes/0
Extra: 01064e3e6b40b4966ca47d3c832d2d0640085415a0c992687d6a7cc7680daae4c7021100000002b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 11dfcf1c67943cedefe6b12a06bcac55adfdefbc3d2ebabd6543ee8620ea8fd9 0.000600000000 1854874 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": 1366845, "vin": [ { "gen": { "height": 1366835 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11dfcf1c67943cedefe6b12a06bcac55adfdefbc3d2ebabd6543ee8620ea8fd9" } } ], "extra": [ 1, 6, 78, 62, 107, 64, 180, 150, 108, 164, 125, 60, 131, 45, 45, 6, 64, 8, 84, 21, 160, 201, 146, 104, 125, 106, 124, 199, 104, 13, 170, 228, 199, 2, 17, 0, 0, 0, 2, 178, 247, 132, 196, 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: