← previous blocknext block →recent activity

Analyzing

Block #86,153,970

25 transactions · 17 stateful · 2026-07-07 08:12:22 UTC

Parallelism

76/100

Blocked

47%

Avg conflicts / tx

0.56

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,153,970  ·  25 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

0xc20b58e0…9719

0xd32edf…ff58

9 touches
10 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x157dbfb2…4089

0x34b655…2a6f

4 touches
1 conflict

0x94dabb65…43a3

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0xec0e0220…cb90

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

10 conflicts on slot 0xc20b58e0af…829719

← previous block·next block →recent activity