Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ed105a10696bbf7c5af5ed37d7390412e8ec0e079453793ff4ed724657f1eb2

Tx prefix hash: 8f3234ffade83f82b706e234cce62d7fe92900c1b4614fac6a6d949c9dab3b09
Tx public key: a0bf0c87342215d498d865bd07036ca103189752da9ffd261568a4dfdc451772
Timestamp: 1642756243 Timestamp [UTC]: 2022-01-21 09:10:43 Age [y:d:h:m:s]: 04:302:06:26:20
Block: 421985 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1259233 RingCT/type: yes/0
Extra: 01a0bf0c87342215d498d865bd07036ca103189752da9ffd261568a4dfdc451772021100000027db0c7f64000000000000000000

1 output(s) for total of 0.024535586951 xmr

stealth address amount amount idx tag
00: 6f5a1541f90ac1c339a32d1caad98147be2e8caaa0aa15016cd3f6756b9d2914 0.024535586951 829708 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": 421995, "vin": [ { "gen": { "height": 421985 } } ], "vout": [ { "amount": 24535586951, "target": { "key": "6f5a1541f90ac1c339a32d1caad98147be2e8caaa0aa15016cd3f6756b9d2914" } } ], "extra": [ 1, 160, 191, 12, 135, 52, 34, 21, 212, 152, 216, 101, 189, 7, 3, 108, 161, 3, 24, 151, 82, 218, 159, 253, 38, 21, 104, 164, 223, 220, 69, 23, 114, 2, 17, 0, 0, 0, 39, 219, 12, 127, 100, 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: