Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 056dcdae6dbf2bfb08df499b6bff47cb4711d878f0cab3125a7eaf6d0feb0ad7

Tx prefix hash: bff20e8e5e710c4ee43fdee8c43354ade35b0badcfb32d7a84a580faf1c06701
Tx public key: 337a08ab4e964cbcba6294ab4534d4fabdff965e98c56a96f7ce732273dcbe33
Timestamp: 1790363565 Timestamp [UTC]: 2026-09-25 19:12:45 Age [y:d:h:m:s]: 00:050:21:02:38
Block: 1643479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 35536 RingCT/type: yes/0
Extra: 01337a08ab4e964cbcba6294ab4534d4fabdff965e98c56a96f7ce732273dcbe33

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1a43f489257c6e71832ee37857e77017ec5c695d04aa2fc69c06d91f77ea9869 0.000600000000 2133563 of 15 <f0>

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": 1643489, "vin": [ { "gen": { "height": 1643479 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "1a43f489257c6e71832ee37857e77017ec5c695d04aa2fc69c06d91f77ea9869", "view_tag": "f0" } } } ], "extra": [ 1, 51, 122, 8, 171, 78, 150, 76, 188, 186, 98, 148, 171, 69, 52, 212, 250, 189, 255, 150, 94, 152, 197, 106, 150, 247, 206, 115, 34, 115, 220, 190, 51 ], "rct_signatures": { "type": 0 } }


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