Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0a4982aadd451d9b02eb9af3da519cdcca6a75e1600fd4ca383cc1e20aec38c

Tx prefix hash: 3b142284e3d772fe265896c0d09d14748ec34d7b100fe3f0c294a241133d0ae2
Tx public key: b2fc01e72b29e439599615e99ef1e2fd446232742625ff12eafe377b0b9d2623
Timestamp: 1680830350 Timestamp [UTC]: 2023-04-07 01:19:10 Age [y:d:h:m:s]: 03:042:04:14:22
Block: 733340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 803095 RingCT/type: yes/0
Extra: 01b2fc01e72b29e439599615e99ef1e2fd446232742625ff12eafe377b0b9d26230211000000015029cbac000000000000000000

1 output(s) for total of 0.002281079301 xmr

stealth address amount amount idx tag
00: 532fa983df673f150fb7bab1954371be6cfcaeb82dd8bef9dd467bd01a5893fa 0.002281079301 1179383 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": 733350, "vin": [ { "gen": { "height": 733340 } } ], "vout": [ { "amount": 2281079301, "target": { "key": "532fa983df673f150fb7bab1954371be6cfcaeb82dd8bef9dd467bd01a5893fa" } } ], "extra": [ 1, 178, 252, 1, 231, 43, 41, 228, 57, 89, 150, 21, 233, 158, 241, 226, 253, 68, 98, 50, 116, 38, 37, 255, 18, 234, 254, 55, 123, 11, 157, 38, 35, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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: