← previous blocknext block →recent activity

Analyzing

Block #98,664,911

21 transactions · 21 stateful · 2026-08-24 04:34:49 UTC

Parallelism

76/100

Blocked

38%

Avg conflicts / tx

0.71

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #98,664,911  ·  21 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

0xa1087a5c…66c4

0x754704…b603

10 touches
10 conflicts

0x11b69a7e…334e

0xee8c0e…1242

8 touches
6 conflicts

0x4d1b5300…1dfa

0xd32edf…ff58

5 touches
3 conflicts

0x2a9e9bd1…5368

0x2a68ba…90c5

4 touches
1 conflict

0x002fed35…79fa

0x2a68ba…90c5

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x92385428…6941

0x34b655…2a6f

4 touches
1 conflict

0xf98db8ee…a56d

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: USDC (USDC)

10 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity