Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2bf308d98c8e2f9e08941e71e859a74ae805807ce714753839c7b6755bc1fab

Tx prefix hash: 02fb7ce8ad459e9f6e5d9fbfd02a289a30427aa79bb87d7f62496f77aec7f6ea
Tx public key: 71ad7a22e509882c4d5fddbfecb7961ff913edcb534e734030fff8f8f5bb6bd6
Timestamp: 1710650405 Timestamp [UTC]: 2024-03-17 04:40:05 Age [y:d:h:m:s]: 02:247:16:12:24
Block: 980061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 702088 RingCT/type: yes/0
Extra: 0171ad7a22e509882c4d5fddbfecb7961ff913edcb534e734030fff8f8f5bb6bd60211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e19885149df214c75ecf74512f3d324267b55fbe73073616b19c0998c8aa5fdc 0.000600000000 1440120 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": 980071, "vin": [ { "gen": { "height": 980061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e19885149df214c75ecf74512f3d324267b55fbe73073616b19c0998c8aa5fdc" } } ], "extra": [ 1, 113, 173, 122, 34, 229, 9, 136, 44, 77, 95, 221, 191, 236, 183, 150, 31, 249, 19, 237, 203, 83, 78, 115, 64, 48, 255, 248, 248, 245, 187, 107, 214, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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: