← previous blocknext block →recent activity

Analyzing

Block #95,372,383

40 transactions · 24 stateful · 2026-08-12 14:44:50 UTC

Parallelism

90/100

Blocked

29%

Avg conflicts / tx

0.23

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #95,372,383  ·  40 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xdd70bea3…1ffe

0x3bd359…433a

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xb33ff823…1188

0x065c9d…c394

6 touches
3 conflicts

0x160f117d…8e90

0x065c9d…c394

4 touches
1 conflict

0x9a555477…19a8

0x754704…b603

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0xf6cc7de8…0b4a

0x3bd359…433a

4 touches
1 conflict

What's blocking what?

Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.

The bottleneck

Throughput-killer: Wrapped MON (WMON)

3 conflicts on slot 0xdd70bea3b0…701ffe

← previous block·next block →recent activity