Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50de27ee12ecd2c94efa15bfa5f0cb5de790f7a4c568db1f9590fe8b9ed1acd2

Tx prefix hash: 76dabc71fdbd79ba7cf164998efd7f3c1d2c5752371613aeb376f1f9c83239e5
Tx public key: 0f03f1d3c46bf88d9b01060d09537f460b7494f0f84e5ecc6b624bd1da9e1e9f
Timestamp: 1785084315 Timestamp [UTC]: 2026-07-26 16:45:15 Age [y:d:h:m:s]: 00:118:03:32:52
Block: 1590861 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 92633 RingCT/type: yes/0
Extra: 010f03f1d3c46bf88d9b01060d09537f460b7494f0f84e5ecc6b624bd1da9e1e9f

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a65a9a9de4fbc2533252351a644fb1a93863bf10b04a64a25ea3b8eacbec4f83 0.000600000000 2080879 of 15 <56>

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": 1590871, "vin": [ { "gen": { "height": 1590861 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "a65a9a9de4fbc2533252351a644fb1a93863bf10b04a64a25ea3b8eacbec4f83", "view_tag": "56" } } } ], "extra": [ 1, 15, 3, 241, 211, 196, 107, 248, 141, 155, 1, 6, 13, 9, 83, 127, 70, 11, 116, 148, 240, 248, 78, 94, 204, 107, 98, 75, 209, 218, 158, 30, 159 ], "rct_signatures": { "type": 0 } }


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