Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a988f0011d2edd97afcd90f7bb5197f2aa9103d762a4fa7a3284ded152065db

Tx prefix hash: c4a1f54ea0696ddde580b013a6866351029a97348521b331d3dbe9069f9d1369
Tx public key: 8b71d17f3aaaedcb5cd6ed70118b9b0c4bdaa5f5af4c588afd263f6e52151e10
Timestamp: 1780440662 Timestamp [UTC]: 2026-06-02 22:51:02 Age [y:d:h:m:s]: 00:167:01:22:36
Block: 1549726 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 130286 RingCT/type: yes/0
Extra: 018b71d17f3aaaedcb5cd6ed70118b9b0c4bdaa5f5af4c588afd263f6e52151e10

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0cbf18070ea43a72a3564bc45a8215e2732d62db81fb3bfcaa70763c41e0db33 0.000600000000 2039700 of 15 <76>

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": 1549736, "vin": [ { "gen": { "height": 1549726 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "0cbf18070ea43a72a3564bc45a8215e2732d62db81fb3bfcaa70763c41e0db33", "view_tag": "76" } } } ], "extra": [ 1, 139, 113, 209, 127, 58, 170, 237, 203, 92, 214, 237, 112, 17, 139, 155, 12, 75, 218, 165, 245, 175, 76, 88, 138, 253, 38, 63, 110, 82, 21, 30, 16 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: