Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b9e2080eb54ecbb1fc01439e875bd338567a683f20b07777893e11812efcd74

Tx prefix hash: b4d8ae12f2489892db608522152641f2d6d9207fed3fb08e130df93f618236e1
Tx public key: b3d328ab692f05ce1305701d91f411c41e83d1c903ec7dc63fd83f5380e832c7
Timestamp: 1749314088 Timestamp [UTC]: 2025-06-07 16:34:48 Age [y:d:h:m:s]: 00:343:03:09:01
Block: 1300042 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235282 RingCT/type: yes/0
Extra: 01b3d328ab692f05ce1305701d91f411c41e83d1c903ec7dc63fd83f5380e832c7021100000001bf51b2a2000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9bc61ed8eac3a15379106cc02f1073684271dc89acff8b60105798e9a54cc230 0.000600000000 1787587 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": 1300052, "vin": [ { "gen": { "height": 1300042 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9bc61ed8eac3a15379106cc02f1073684271dc89acff8b60105798e9a54cc230" } } ], "extra": [ 1, 179, 211, 40, 171, 105, 47, 5, 206, 19, 5, 112, 29, 145, 244, 17, 196, 30, 131, 209, 201, 3, 236, 125, 198, 63, 216, 63, 83, 128, 232, 50, 199, 2, 17, 0, 0, 0, 1, 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: