← previous blocknext block →recent activity

Analyzing

Block #98,659,889

19 transactions · 18 stateful · 2026-08-24 04:08:39 UTC

Parallelism

74/100

Blocked

44%

Avg conflicts / tx

0.79

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #98,659,889  ·  19 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

0x2a9e9bd1…5368

0x2a68ba…90c5

10 touches
10 conflicts

0xa1087a5c…66c4

0x754704…b603

10 touches
10 conflicts

0x7c9996a0…33a6

0xa6afd3…d132

10 touches
10 conflicts

0x61ca6437…2142

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x81ceb686…4df3

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