Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: affa809cdbfe3373c3150b3a07327c11edbbab9ead742d23c84cece0805cc16c

Tx prefix hash: 3788f2afc7c182a2bf7fd1be69efa69a2112c302e21b59daed03a321c0fa2b39
Tx public key: 84f0eac2644296006259e20c3bf48f7946eaaee9f1a803344714d25f4be463f1
Timestamp: 1747760870 Timestamp [UTC]: 2025-05-20 17:07:50 Age [y:d:h:m:s]: 01:182:15:54:44
Block: 1287170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394604 RingCT/type: yes/0
Extra: 0184f0eac2644296006259e20c3bf48f7946eaaee9f1a803344714d25f4be463f10211000000019f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b6af9350e3e63bd109b6c5ddafb407c11ea1db90add07b314767df3a20d40551 0.000600000000 1774637 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": 1287180, "vin": [ { "gen": { "height": 1287170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6af9350e3e63bd109b6c5ddafb407c11ea1db90add07b314767df3a20d40551" } } ], "extra": [ 1, 132, 240, 234, 194, 100, 66, 150, 0, 98, 89, 226, 12, 59, 244, 143, 121, 70, 234, 174, 233, 241, 168, 3, 52, 71, 20, 210, 95, 75, 228, 99, 241, 2, 17, 0, 0, 0, 1, 159, 159, 230, 140, 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: