← previous blocknext block →recent activity

Analyzing

Block #98,744,253

22 transactions · 17 stateful · 2026-08-24 11:19:37 UTC

Parallelism

86/100

Blocked

35%

Avg conflicts / tx

0.32

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #98,744,253  ·  22 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0x2b54cadb…4425

0xd18b7e…414b

6 touches
3 conflicts

0x0fed2d3b…1c10

0x40c49f…2af0

4 touches
1 conflict

0xe5bb3628…e5f1

0x34b655…2a6f

4 touches
1 conflict

0x6518075e…2b17

0x2a68ba…90c5

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x261cbea7…e35d

0x34b655…2a6f

4 touches
1 conflict

0x261cbea7…e35e

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)

3 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity