Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0afcb817306e667c7704f954508cfef3ada5fcc3048bbe92a5d105e7abfdb849

Tx prefix hash: 3219f8d812b3addef612832eb4e82d330e3cc2cb7bdccb3b85a588782bff3f3b
Tx public key: 1ea26ad06d24f8672351334d76d1a7d9c24e300a2462cff00f0ac7ddf757e8a3
Timestamp: 1749580259 Timestamp [UTC]: 2025-06-10 18:30:59 Age [y:d:h:m:s]: 01:163:06:44:36
Block: 1302231 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380840 RingCT/type: yes/0
Extra: 011ea26ad06d24f8672351334d76d1a7d9c24e300a2462cff00f0ac7ddf757e8a3021100000002e4dc9009000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ae7e24440c96d839989edcaa23ffc096a9acb9903b9256de6af555dfea334fe9 0.000600000000 1789800 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": 1302241, "vin": [ { "gen": { "height": 1302231 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae7e24440c96d839989edcaa23ffc096a9acb9903b9256de6af555dfea334fe9" } } ], "extra": [ 1, 30, 162, 106, 208, 109, 36, 248, 103, 35, 81, 51, 77, 118, 209, 167, 217, 194, 78, 48, 10, 36, 98, 207, 240, 15, 10, 199, 221, 247, 87, 232, 163, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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: