Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 866cbecdfb678c506662f66b9a5eba96ea480e1c85bf1b63a103d17029f2aee2

Tx prefix hash: 6cb779688b8d6bbf79bd3b6f1c13d446d93158e8f3f02a10ce58f70c4347e16c
Tx public key: 770e2477a1244c3455141bb0cefbac175565af29b90024c8bf6b55223e04dd72
Timestamp: 1709421063 Timestamp [UTC]: 2024-03-02 23:11:03 Age [y:d:h:m:s]: 02:257:03:33:30
Block: 969848 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 708733 RingCT/type: yes/0
Extra: 01770e2477a1244c3455141bb0cefbac175565af29b90024c8bf6b55223e04dd7202110000000552d47e94000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3bb4921c2b0003f4f0f606ca9ec729d88366d1cd59c33445cb1890d5897faab3 0.000600000000 1429697 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": 969858, "vin": [ { "gen": { "height": 969848 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3bb4921c2b0003f4f0f606ca9ec729d88366d1cd59c33445cb1890d5897faab3" } } ], "extra": [ 1, 119, 14, 36, 119, 161, 36, 76, 52, 85, 20, 27, 176, 206, 251, 172, 23, 85, 101, 175, 41, 185, 0, 36, 200, 191, 107, 85, 34, 62, 4, 221, 114, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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: