Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5a8562bdff76c03b47b66560c5ad0d15d8e8001a08ef6a34fc66cc2018dfb25

Tx prefix hash: 09991da3a10be0e697623b6f4edae4a0b542a08fffcd797faeb3808c81cc7895
Tx public key: 6e432770aaa990f99deed10f040ad7f9be6483d15310d74b9f21ad4ed743e37d
Timestamp: 1763123600 Timestamp [UTC]: 2025-11-14 12:33:20 Age [y:d:h:m:s]: 01:007:07:50:44
Block: 1411948 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271546 RingCT/type: yes/0
Extra: 016e432770aaa990f99deed10f040ad7f9be6483d15310d74b9f21ad4ed743e37d021100000002d6e19d7c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ba1471d2833c200c0b8b666d63981629f2dcf4e0d401ed18c6cf2567bebdf63a 0.000600000000 1900413 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": 1411958, "vin": [ { "gen": { "height": 1411948 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba1471d2833c200c0b8b666d63981629f2dcf4e0d401ed18c6cf2567bebdf63a" } } ], "extra": [ 1, 110, 67, 39, 112, 170, 169, 144, 249, 157, 238, 209, 15, 4, 10, 215, 249, 190, 100, 131, 209, 83, 16, 215, 75, 159, 33, 173, 78, 215, 67, 227, 125, 2, 17, 0, 0, 0, 2, 214, 225, 157, 124, 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: