Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e477d226fa8a95c68ec5a048d89f3bbd165e4b925af1859f42f968b76eace7f4

Tx prefix hash: c0f42b34d2fa553710e3c6e640d921393ac7c38c804cdaa83c3b5be85f59e024
Tx public key: 1634381f1ebf9f5f482dbbb189efd8f34950f47b8a1eaff79b63f89c6a21c66f
Timestamp: 1775004804 Timestamp [UTC]: 2026-04-01 00:53:24 Age [y:d:h:m:s]: 00:227:00:09:52
Block: 1510161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167622 RingCT/type: yes/0
Extra: 011634381f1ebf9f5f482dbbb189efd8f34950f47b8a1eaff79b63f89c6a21c66f021100000001e3d7dc9f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 34c638321a72121cb4ccd9fea279ee5c520b83fad7b896d4a02efa895abc576f 0.000600000000 1999939 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": 1510171, "vin": [ { "gen": { "height": 1510161 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34c638321a72121cb4ccd9fea279ee5c520b83fad7b896d4a02efa895abc576f" } } ], "extra": [ 1, 22, 52, 56, 31, 30, 191, 159, 95, 72, 45, 187, 177, 137, 239, 216, 243, 73, 80, 244, 123, 138, 30, 175, 247, 155, 99, 248, 156, 106, 33, 198, 111, 2, 17, 0, 0, 0, 1, 227, 215, 220, 159, 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: