Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5bdd83b768910ccb76c1cfce55fe8bae083da18f58d5f326e373ba7b83ec75a

Tx prefix hash: fd52d8e1cca200288a99d01ba8e74aecd5a6d70dc5600f745f60be7455035faf
Tx public key: 1dc3b95c257fea2588d8bd20c8f68df57d2aee71eb7fe9f405b0478cfb62db2b
Timestamp: 1749368555 Timestamp [UTC]: 2025-06-08 07:42:35 Age [y:d:h:m:s]: 00:354:04:42:37
Block: 1300486 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244856 RingCT/type: yes/0
Extra: 011dc3b95c257fea2588d8bd20c8f68df57d2aee71eb7fe9f405b0478cfb62db2b021100000004bf51b2a2000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 253f2800b6282a8c21e0a4763d40d37648443d3abf8fbcdcb2c29559abdfa878 0.000600000000 1788035 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": 1300496, "vin": [ { "gen": { "height": 1300486 } } ], "vout": [ { "amount": 600000000, "target": { "key": "253f2800b6282a8c21e0a4763d40d37648443d3abf8fbcdcb2c29559abdfa878" } } ], "extra": [ 1, 29, 195, 185, 92, 37, 127, 234, 37, 136, 216, 189, 32, 200, 246, 141, 245, 125, 42, 238, 113, 235, 127, 233, 244, 5, 176, 71, 140, 251, 98, 219, 43, 2, 17, 0, 0, 0, 4, 191, 81, 178, 162, 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: