← previous blocknext block →recent activity

Analyzing

Block #98,646,642

23 transactions · 20 stateful · 2026-08-24 02:59:22 UTC

Parallelism

78/100

Blocked

35%

Avg conflicts / tx

0.65

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #98,646,642  ·  23 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x11b69a7e…334e

0xee8c0e…1242

10 touches
10 conflicts

0xa1087a5c…66c4

0x754704…b603

10 touches
10 conflicts

0x2a9e9bd1…5368

0x2a68ba…90c5

8 touches
6 conflicts

0x54ec1fdb…a69c

0xa6afd3…d132

8 touches
6 conflicts

0x7de57974…f5ba

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x1641b5fc…fa40

0x34b655…2a6f

4 touches
1 conflict

0x62910921…3016

0x34b655…2a6f

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 Ether (WETH)

10 conflicts on slot 0x11b69a7ea1…83334e

← previous block·next block →recent activity