Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a4371ffca947f7703af6c9abc030273c864245bcefe5fcd501d14b2ef110ab3

Tx prefix hash: 556276dd7a8ad90d145d100dd3433ad809689d61454a3b14ef4a38eb9eea021e
Tx public key: 09262ef13938cd1a34f322e1a4bdd19035e7202b25328aec994fec1f5604d12a
Timestamp: 1747196680 Timestamp [UTC]: 2025-05-14 04:24:40 Age [y:d:h:m:s]: 00:363:21:48:03
Block: 1282495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250031 RingCT/type: yes/0
Extra: 0109262ef13938cd1a34f322e1a4bdd19035e7202b25328aec994fec1f5604d12a0211000000039f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1d53b6d5696e17ec2ddbd353b25fbbde0ec2c7302912aace81335cbccf4e7a9f 0.000600000000 1769902 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": 1282505, "vin": [ { "gen": { "height": 1282495 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d53b6d5696e17ec2ddbd353b25fbbde0ec2c7302912aace81335cbccf4e7a9f" } } ], "extra": [ 1, 9, 38, 46, 241, 57, 56, 205, 26, 52, 243, 34, 225, 164, 189, 209, 144, 53, 231, 32, 43, 37, 50, 138, 236, 153, 79, 236, 31, 86, 4, 209, 42, 2, 17, 0, 0, 0, 3, 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: