Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfa11ed9b9eca19d71acba080eee82ea02769c9104b1cc664c77c5675ba6c153

Tx prefix hash: 97fd689c30ae087d7ea486cdd3d663bb26c039c3d1a7382481bd29df09c255e8
Tx public key: d9b6806af13fa791bf71c7cdba08b0f807acae0c3395234cbb08ddfa5d0b9444
Timestamp: 1675975307 Timestamp [UTC]: 2023-02-09 20:41:47 Age [y:d:h:m:s]: 03:092:07:32:29
Block: 693450 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 838381 RingCT/type: yes/0
Extra: 01d9b6806af13fa791bf71c7cdba08b0f807acae0c3395234cbb08ddfa5d0b9444021100000001faf35c9c000000000000000000

1 output(s) for total of 0.003092517800 xmr

stealth address amount amount idx tag
00: c32eeea45e473bb23f75336ec939da852a5ed3dad2418c61977ebd45a81313df 0.003092517800 1136339 of 0 -

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": 693460, "vin": [ { "gen": { "height": 693450 } } ], "vout": [ { "amount": 3092517800, "target": { "key": "c32eeea45e473bb23f75336ec939da852a5ed3dad2418c61977ebd45a81313df" } } ], "extra": [ 1, 217, 182, 128, 106, 241, 63, 167, 145, 191, 113, 199, 205, 186, 8, 176, 248, 7, 172, 174, 12, 51, 149, 35, 76, 187, 8, 221, 250, 93, 11, 148, 68, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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: