← previous blocknext block →recent activity

Analyzing

Block #106,008,554

38 transactions · 25 stateful · 2026-09-18 22:20:07 UTC

Parallelism

74/100

Blocked

56%

Avg conflicts / tx

1.26

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #106,008,554  ·  38 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x2e0b2988…d877

0xd32edf…ff58

13 touches
21 conflicts

0x839c0c71…bada

0x34b655…2a6f

12 touches
15 conflicts

0x94dabb65…43a3

0x34b655…2a6f

10 touches
10 conflicts

0xca841faa…486a

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…002b

0x1b6862…e19c

8 touches
6 conflicts

0x8d47c9a4…f11d

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x1e9a3afd…a6e5

0x34b655…2a6f

8 touches
6 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

21 conflicts on slot 0x2e0b2988e5…f7d877

← previous block·next block →recent activity