← previous blocknext block →recent activity

Analyzing

Block #87,319,334

19 transactions · 18 stateful · 2026-07-12 18:02:40 UTC

Parallelism

68/100

Blocked

56%

Avg conflicts / tx

1.26

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #87,319,334  ·  19 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

0x2390540c…b339

0xd32edf…ff58

11 touches
15 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4ab

0x34b655…2a6f

6 touches
3 conflicts

0x974c36fe…1cd7

0x34b655…2a6f

6 touches
3 conflicts

0xa3c36de0…3cf3

0x34b655…2a6f

6 touches
3 conflicts

0x033dddd2…ac15

0x34b655…2a6f

4 touches
1 conflict

0x22af2208…099e

0x34b655…2a6f

4 touches
1 conflict

0x4a6982a4…158c

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

15 conflicts on slot 0x2390540c0f…25b339

← previous block·next block →recent activity