Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5306992566099cb9ff9c45c4fc44b1460994c9fa7f434c4e1a064fbe3dabed7f

Tx prefix hash: 65c23775b64500a4fb3e83c7b4d83aa4dd1fe06effd982f85baac6c28682d89f
Tx public key: e0425044bdc2c31c7ab79fc1e7413b2fda4513c1896074f5c762993a5e00d9f2
Timestamp: 1750582925 Timestamp [UTC]: 2025-06-22 09:02:05 Age [y:d:h:m:s]: 01:150:02:40:23
Block: 1310342 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371517 RingCT/type: yes/0
Extra: 01e0425044bdc2c31c7ab79fc1e7413b2fda4513c1896074f5c762993a5e00d9f2021100000009bf51b2a2000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8fec184fb04bb12c80e5d4208060c7b20b8dac2d3f45ee5a9c971ef4e68d9aec 0.000600000000 1797961 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": 1310352, "vin": [ { "gen": { "height": 1310342 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8fec184fb04bb12c80e5d4208060c7b20b8dac2d3f45ee5a9c971ef4e68d9aec" } } ], "extra": [ 1, 224, 66, 80, 68, 189, 194, 195, 28, 122, 183, 159, 193, 231, 65, 59, 47, 218, 69, 19, 193, 137, 96, 116, 245, 199, 98, 153, 58, 94, 0, 217, 242, 2, 17, 0, 0, 0, 9, 191, 81, 178, 162, 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: