Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a82039b550c6f7202fc98ff04438f5a3dcd3a98b9b5fddf93d7af78faf126e3b

Tx prefix hash: 585ee21f9ac2d6295c6fd7c5defa53f991a4dd5c11293200948d63f58058f588
Tx public key: 28eb6c53cd9787d170af5d387d20cd48330adcddc72cd4a42ebeab322c3879a7
Timestamp: 1773366178 Timestamp [UTC]: 2026-03-13 01:42:58 Age [y:d:h:m:s]: 00:247:12:12:37
Block: 1496628 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182314 RingCT/type: yes/0
Extra: 0128eb6c53cd9787d170af5d387d20cd48330adcddc72cd4a42ebeab322c3879a7021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2b589067df16b3ca4407fac64fb040d6a7fec415df7391f1e20d29483f19f454 0.000600000000 1986254 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": 1496638, "vin": [ { "gen": { "height": 1496628 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b589067df16b3ca4407fac64fb040d6a7fec415df7391f1e20d29483f19f454" } } ], "extra": [ 1, 40, 235, 108, 83, 205, 151, 135, 209, 112, 175, 93, 56, 125, 32, 205, 72, 51, 10, 220, 221, 199, 44, 212, 164, 46, 190, 171, 50, 44, 56, 121, 167, 2, 17, 0, 0, 0, 2, 228, 245, 25, 63, 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: