Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56b2e2208cdfa9192520eae5af5f89612df968254f8fcc3eb2bf4a975ba5d464

Tx prefix hash: fb9473a1c964e929bfe39e7e8461c000230615bd749a841523e707f7cb6c9034
Tx public key: 20c71c2c775b60987fe8e30af4d379da7be35b97ba746356a5c68450e2868927
Timestamp: 1771154657 Timestamp [UTC]: 2026-02-15 11:24:17 Age [y:d:h:m:s]: 00:273:03:25:07
Block: 1478296 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200667 RingCT/type: yes/0
Extra: 0120c71c2c775b60987fe8e30af4d379da7be35b97ba746356a5c68450e2868927021100000001e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 498b41f2455e0cc53a68d5b4f8f683eb09d3efa90126fdf13d9f62d25b9745e0 0.000600000000 1967624 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": 1478306, "vin": [ { "gen": { "height": 1478296 } } ], "vout": [ { "amount": 600000000, "target": { "key": "498b41f2455e0cc53a68d5b4f8f683eb09d3efa90126fdf13d9f62d25b9745e0" } } ], "extra": [ 1, 32, 199, 28, 44, 119, 91, 96, 152, 127, 232, 227, 10, 244, 211, 121, 218, 123, 227, 91, 151, 186, 116, 99, 86, 165, 198, 132, 80, 226, 134, 137, 39, 2, 17, 0, 0, 0, 1, 228, 245, 25, 63, 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: