← previous blocknext block →recent activity

Analyzing

Block #87,284,357

20 transactions · 16 stateful · 2026-07-12 14:08:50 UTC

Parallelism

65/100

Blocked

63%

Avg conflicts / tx

1.4

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #87,284,357  ·  20 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x8942f32e…239d

0xd32edf…ff58

13 touches
21 conflicts

0xcc616f7f…6178

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0x9aa1ca79…d902

0x34b655…2a6f

6 touches
3 conflicts

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0xbf78ee7f…e7fd

0x34b655…2a6f

6 touches
3 conflicts

0x56f7a389…74fd

0x34b655…2a6f

4 touches
1 conflict

0x7b6c252d…a696

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: FastLane: FastLaneAuctionHandler

21 conflicts on slot 0x8942f32eae…b9239d

← previous block·next block →recent activity