← previous blocknext block →recent activity

Analyzing

Block #86,137,408

23 transactions · 21 stateful · 2026-07-07 06:21:50 UTC

Parallelism

78/100

Blocked

33%

Avg conflicts / tx

0.57

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,137,408  ·  23 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

0x083d0c2f…b66a

0xd32edf…ff58

9 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0x89999c15…fdac

0x34b655…2a6f

4 touches
1 conflict

0x5677a5c5…ddbb

0xa6afd3…d132

4 touches
1 conflict

0x66f473d3…2d03

0xa6afd3…d132

4 touches
1 conflict

0x518f2037…e422

0xa6afd3…d132

4 touches
1 conflict

0xd52a8c24…d848

0xa6afd3…d132

3 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

10 conflicts on slot 0x083d0c2f95…95b66a

← previous block·next block →recent activity