Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf8d5a99be33b7a33bc764cad945bc0921183e7362ebd896675e251780eb3d7e

Tx prefix hash: cf2db236cfa1f4f13c436a25d3938c8e7c63cb2d82e690e378d8d0655546bf0f
Tx public key: acebf171eaaf9e888b3ae44c1a3d3a10284ad0c1ff4cc44a0cb1cb61bf6b7bb4
Timestamp: 1787597475 Timestamp [UTC]: 2026-08-24 18:51:15 Age [y:d:h:m:s]: 00:089:23:20:46
Block: 1620138 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 63356 RingCT/type: yes/0
Extra: 01acebf171eaaf9e888b3ae44c1a3d3a10284ad0c1ff4cc44a0cb1cb61bf6b7bb4

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c646c50337f4f9f0a308214a5fdc57a9a564f9a183574f97aa5a487ec0c3ff94 0.000600000000 2110158 of 15 <b4>

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": 1620148, "vin": [ { "gen": { "height": 1620138 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "c646c50337f4f9f0a308214a5fdc57a9a564f9a183574f97aa5a487ec0c3ff94", "view_tag": "b4" } } } ], "extra": [ 1, 172, 235, 241, 113, 234, 175, 158, 136, 139, 58, 228, 76, 26, 61, 58, 16, 40, 74, 208, 193, 255, 76, 196, 74, 12, 177, 203, 97, 191, 107, 123, 180 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: