Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1a25fd68d2ee40162c37bb5c96af6423fafa2aec6ef51ce79d76719a08e6ff2

Tx prefix hash: 68276f6f3a791ac25ace41800e7aa885cedb4781f614f364370051e9a120eb78
Tx public key: 69df0938113b123c5e259fba96b989621946107c93c40f629a22e74c8f7457bb
Timestamp: 1758179554 Timestamp [UTC]: 2025-09-18 07:12:34 Age [y:d:h:m:s]: 01:065:09:50:42
Block: 1370977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312517 RingCT/type: yes/0
Extra: 0169df0938113b123c5e259fba96b989621946107c93c40f629a22e74c8f7457bb021100000002b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8b59501b73a812936b4c6a98536f33cde7f3c97370a15a4e1af641a643ad0309 0.000600000000 1859054 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": 1370987, "vin": [ { "gen": { "height": 1370977 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b59501b73a812936b4c6a98536f33cde7f3c97370a15a4e1af641a643ad0309" } } ], "extra": [ 1, 105, 223, 9, 56, 17, 59, 18, 60, 94, 37, 159, 186, 150, 185, 137, 98, 25, 70, 16, 124, 147, 196, 15, 98, 154, 34, 231, 76, 143, 116, 87, 187, 2, 17, 0, 0, 0, 2, 178, 247, 132, 196, 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: