Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a95367bf7e369965c0a667f2fdae82f020a176967d74f836f8cb5a1be2a9ebfa

Tx prefix hash: 57c31626461b306d70e075b2c29503d8089760ec40bac6506b6e88d59bb062ad
Tx public key: ffa8a92afe408398512a31162ed1cf98b603b2c2271d24729b25890b14e1cad1
Timestamp: 1774250131 Timestamp [UTC]: 2026-03-23 07:15:31 Age [y:d:h:m:s]: 00:238:04:57:15
Block: 1503907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175735 RingCT/type: yes/0
Extra: 01ffa8a92afe408398512a31162ed1cf98b603b2c2271d24729b25890b14e1cad1021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a27809b44ef8e48e9c5e9bb61643dd273fd4bbef0758b5fe27f65328d6a19e8b 0.000600000000 1993621 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": 1503917, "vin": [ { "gen": { "height": 1503907 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a27809b44ef8e48e9c5e9bb61643dd273fd4bbef0758b5fe27f65328d6a19e8b" } } ], "extra": [ 1, 255, 168, 169, 42, 254, 64, 131, 152, 81, 42, 49, 22, 46, 209, 207, 152, 182, 3, 178, 194, 39, 29, 36, 114, 155, 37, 137, 11, 20, 225, 202, 209, 2, 17, 0, 0, 0, 3, 241, 136, 200, 168, 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: