← previous blocknext block →recent activity

Analyzing

Block #98,647,506

21 transactions · 20 stateful · 2026-08-24 03:03:53 UTC

Parallelism

71/100

Blocked

40%

Avg conflicts / tx

0.9

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #98,647,506  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

8 touches
6 conflicts

0x889d5e90…929a

0x2a68ba…90c5

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x00000000…0002

0xbb3f3c…e046

6 touches
3 conflicts

0x2a9e9bd1…5368

0x2a68ba…90c5

6 touches
3 conflicts

0xbf29903d…c4bf

0xa6afd3…d132

5 touches
3 conflicts

0x56a44dd6…039d

0xa6afd3…d132

5 touches
3 conflicts

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)

6 conflicts on slot 0x11b69a7ea1…83334e

← previous block·next block →recent activity