Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ccd0d47d7577de40edf8a10dcb868c44580c1585e90bd3b95cdb09419d138ab

Tx prefix hash: f5db8eebcd385901ce9c732313da9f2cc004d679e1062f7c049a3e816499b725
Tx public key: 6279cb0f32153d9c0e1792f236dafe2387b56a7d9e96682e0489de289fa5b3e1
Timestamp: 1748132587 Timestamp [UTC]: 2025-05-25 00:23:07 Age [y:d:h:m:s]: 01:179:03:15:08
Block: 1290254 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 392117 RingCT/type: yes/0
Extra: 016279cb0f32153d9c0e1792f236dafe2387b56a7d9e96682e0489de289fa5b3e1021100000001a11dba98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 79a643cda58b2af7c568da016d44ddf5bd30406decda0eb24c6686e4e0f5e4e5 0.000600000000 1777723 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": 1290264, "vin": [ { "gen": { "height": 1290254 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79a643cda58b2af7c568da016d44ddf5bd30406decda0eb24c6686e4e0f5e4e5" } } ], "extra": [ 1, 98, 121, 203, 15, 50, 21, 61, 156, 14, 23, 146, 242, 54, 218, 254, 35, 135, 181, 106, 125, 158, 150, 104, 46, 4, 137, 222, 40, 159, 165, 179, 225, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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: