← previous blocknext block →recent activity

Analyzing

Block #86,623,809

24 transactions · 20 stateful · 2026-07-09 12:32:45 UTC

Parallelism

71/100

Blocked

55%

Avg conflicts / tx

1.21

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #86,623,809  ·  24 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

0xb107c0bb…6182

0xd32edf…ff58

13 touches
21 conflicts

0x89c7ec3b…85ba

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x14ecd102…be3e

0x34b655…2a6f

4 touches
1 conflict

0x22bc4ea4…5c8a

0x34b655…2a6f

4 touches
1 conflict

0x2b5101ac…090b

0x34b655…2a6f

4 touches
1 conflict

0x5d7f309d…5145

0x34b655…2a6f

4 touches
1 conflict

0x6b2ba712…0214

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 0xb107c0bb68…646182

← previous block·next block →recent activity