← previous blocknext block →recent activity

Analyzing

Block #86,250,265

31 transactions · 21 stateful · 2026-07-07 18:55:26 UTC

Parallelism

81/100

Blocked

38%

Avg conflicts / tx

0.68

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,250,265  ·  31 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

0x26d38ad4…e573

0xd32edf…ff58

11 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x3bdd71a2…b6eb

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001f

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002f

0x1b6862…e19c

4 touches
1 conflict

0x91945265…e592

0x1b6862…e19c

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 0x26d38ad47a…d1e573

← previous block·next block →recent activity