Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f1e14e3e4527e16988d248ec34ce9d1e2f9b65e12d7b8279dd1eeb37dce099d

Tx prefix hash: 927368f3eaf1cc7d5918270a50a4dc858fbd556096aa90ca61ed12ca954536f0
Tx public key: 069f3ac2b8e3ebdd79fc1424d19324f16dc2db7e14046d751ef149f7d2c8ad18
Timestamp: 1774206693 Timestamp [UTC]: 2026-03-22 19:11:33 Age [y:d:h:m:s]: 00:243:07:21:38
Block: 1503544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179559 RingCT/type: yes/0
Extra: 01069f3ac2b8e3ebdd79fc1424d19324f16dc2db7e14046d751ef149f7d2c8ad18021100000008f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a88454032a89982f36c7064faea9ae56314e208bc513d122b41358d718b74f04 0.000600000000 1993256 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": 1503554, "vin": [ { "gen": { "height": 1503544 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a88454032a89982f36c7064faea9ae56314e208bc513d122b41358d718b74f04" } } ], "extra": [ 1, 6, 159, 58, 194, 184, 227, 235, 221, 121, 252, 20, 36, 209, 147, 36, 241, 109, 194, 219, 126, 20, 4, 109, 117, 30, 241, 73, 247, 210, 200, 173, 24, 2, 17, 0, 0, 0, 8, 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: