← previous blocknext block →recent activity

Analyzing

Block #86,103,318

30 transactions · 27 stateful · 2026-07-07 02:34:10 UTC

Parallelism

63/100

Blocked

70%

Avg conflicts / tx

2.27

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #86,103,318  ·  30 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xdb8f57a5…c3bd

0xd32edf…ff58

19 touches
45 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0xd99b3b64…1c95

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…001c

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002c

0x1b6862…e19c

6 touches
3 conflicts

0x0f94ee4c…189b

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

45 conflicts on slot 0xdb8f57a535…dfc3bd

← previous block·next block →recent activity