Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a14dc3927c4edf33d1da1b871db4040fe3700e6f881787ed67e3a0bb09caeff1

Tx prefix hash: 630dfde101cda39acaf6664f8517329a6a67b33ff13bd32243818fc0d1b09bb5
Tx public key: 3e3a28743288d9b4699dcdd05be879ca45d8a2c0bbfee284164b74b2ac296588
Timestamp: 1748231535 Timestamp [UTC]: 2025-05-26 03:52:15 Age [y:d:h:m:s]: 01:179:22:41:09
Block: 1291069 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 392425 RingCT/type: yes/0
Extra: 013e3a28743288d9b4699dcdd05be879ca45d8a2c0bbfee284164b74b2ac2965880211000000019f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 160d0a6f568fa5192a90e518a2610834906a3664229f5c1f7f955984863538c8 0.000600000000 1778540 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": 1291079, "vin": [ { "gen": { "height": 1291069 } } ], "vout": [ { "amount": 600000000, "target": { "key": "160d0a6f568fa5192a90e518a2610834906a3664229f5c1f7f955984863538c8" } } ], "extra": [ 1, 62, 58, 40, 116, 50, 136, 217, 180, 105, 157, 205, 208, 91, 232, 121, 202, 69, 216, 162, 192, 187, 254, 226, 132, 22, 75, 116, 178, 172, 41, 101, 136, 2, 17, 0, 0, 0, 1, 159, 159, 230, 140, 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: