Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1df35147b9d2a1ad5b1fb44f26cf98bf9348ab212937fb2ccc0461e95d51131d

Tx prefix hash: b7a9432172b56021e917d9be1afd8764384255ac128a5b6bcd9651b2c560db8f
Tx public key: fc15022e7c63110c257d6a15daa9c54936b38eaa5493090c3c46cd8baadeba00
Timestamp: 1775114180 Timestamp [UTC]: 2026-04-02 07:16:20 Age [y:d:h:m:s]: 00:231:18:07:03
Block: 1511065 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171231 RingCT/type: yes/0
Extra: 01fc15022e7c63110c257d6a15daa9c54936b38eaa5493090c3c46cd8baadeba00021100000007e3d7dc9f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 742749e7b3ee264dced4e3438d78dc5386c5017ccf33613b12c4b8dbc4a0a1d8 0.000600000000 2000853 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": 1511075, "vin": [ { "gen": { "height": 1511065 } } ], "vout": [ { "amount": 600000000, "target": { "key": "742749e7b3ee264dced4e3438d78dc5386c5017ccf33613b12c4b8dbc4a0a1d8" } } ], "extra": [ 1, 252, 21, 2, 46, 124, 99, 17, 12, 37, 125, 106, 21, 218, 169, 197, 73, 54, 179, 142, 170, 84, 147, 9, 12, 60, 70, 205, 139, 170, 222, 186, 0, 2, 17, 0, 0, 0, 7, 227, 215, 220, 159, 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: