Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2f545c0672d33f2d4cf28a990cbc25518af6591505a748313e0f6d650d50bc2

Tx prefix hash: f79ace6141c235a001f2579f4395222fa4a4ed9f963da6dc3c225645de967c4e
Tx public key: a2c36bcdb487df4a1da9e69eff66b10018adcce27fcdd535beffd70f291d7b05
Timestamp: 1647410499 Timestamp [UTC]: 2022-03-16 06:01:39 Age [y:d:h:m:s]: 04:057:16:55:33
Block: 459469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1072196 RingCT/type: yes/0
Extra: 01a2c36bcdb487df4a1da9e69eff66b10018adcce27fcdd535beffd70f291d7b05021100000006d3fcec30000000000000000000

1 output(s) for total of 0.018432690596 xmr

stealth address amount amount idx tag
00: 7c958f0e00c712377a7704fd5e6695179c3be57e33774645eff04bd41bdbf777 0.018432690596 876214 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": 459479, "vin": [ { "gen": { "height": 459469 } } ], "vout": [ { "amount": 18432690596, "target": { "key": "7c958f0e00c712377a7704fd5e6695179c3be57e33774645eff04bd41bdbf777" } } ], "extra": [ 1, 162, 195, 107, 205, 180, 135, 223, 74, 29, 169, 230, 158, 255, 102, 177, 0, 24, 173, 204, 226, 127, 205, 213, 53, 190, 255, 215, 15, 41, 29, 123, 5, 2, 17, 0, 0, 0, 6, 211, 252, 236, 48, 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: