← previous blocknext block →recent activity

Analyzing

Block #86,981,440

31 transactions · 22 stateful · 2026-07-11 04:23:35 UTC

Parallelism

58/100

Blocked

68%

Avg conflicts / tx

2.71

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #86,981,440  ·  31 txs across 13 waves  ·  depth 13
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

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

0x444d8ba5…0d98

0xd32edf…ff58

25 touches
78 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0x0733be30…112f

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…002e

0x1b6862…e19c

6 touches
3 conflicts

0xd5b10148…e637

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

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

78 conflicts on slot 0x444d8ba5cc…750d98

← previous block·next block →recent activity