← previous blocknext block →recent activity

Analyzing

Block #97,517,715

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

Parallelism

76/100

Blocked

33%

Avg conflicts / tx

0.67

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #97,517,715  ·  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

0xe169a428…4b03

0x065c9d…c394

6 touches
3 conflicts

0x0778475b…bd75

0x2a68ba…90c5

6 touches
3 conflicts

0xa7013be2…c0a8

0x34b655…2a6f

6 touches
3 conflicts

0x4353473d…dcc2

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x5ffc25fa…b119

0x34b655…2a6f

4 touches
1 conflict

0x69ee34d1…30f8

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