Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f2c2cf9bb8a08a3362507f151245cd4d7cc306a47fb45eb66eb5211fbe73dad

Tx prefix hash: 96757884507c82a4a20a79214300b8927b3b1068a9ecbd6b31b77dc1d9a41fb4
Tx public key: d2ad97b4b60480b85accdc803619acaa37128f9a3ab148f79eed182338f1c64b
Timestamp: 1773851350 Timestamp [UTC]: 2026-03-18 16:29:10 Age [y:d:h:m:s]: 00:241:02:24:35
Block: 1500601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177741 RingCT/type: yes/0
Extra: 01d2ad97b4b60480b85accdc803619acaa37128f9a3ab148f79eed182338f1c64b021100000009f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b40f767887a638db6bd3a71d4bec4cd2d1d75700f9fabfe3069b5846d8f77e67 0.000600000000 1990275 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": 1500611, "vin": [ { "gen": { "height": 1500601 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b40f767887a638db6bd3a71d4bec4cd2d1d75700f9fabfe3069b5846d8f77e67" } } ], "extra": [ 1, 210, 173, 151, 180, 182, 4, 128, 184, 90, 204, 220, 128, 54, 25, 172, 170, 55, 18, 143, 154, 58, 177, 72, 247, 158, 237, 24, 35, 56, 241, 198, 75, 2, 17, 0, 0, 0, 9, 241, 136, 200, 168, 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: