← previous blocknext block →recent activity

Analyzing

Block #105,855,892

26 transactions · 22 stateful · 2026-09-18 09:30:43 UTC

Parallelism

73/100

Blocked

55%

Avg conflicts / tx

1.42

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #105,855,892  ·  26 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

0x5a229009…8e89

0xd32edf…ff58

13 touches
21 conflicts

0x06c7982c…1303

0x34b655…2a6f

12 touches
15 conflicts

0xf8e6479f…f193

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x4be9812b…48a9

0x34b655…2a6f

6 touches
3 conflicts

0xab981df1…2941

0x34b655…2a6f

6 touches
3 conflicts

0xfefb0189…f726

0x34b655…2a6f

6 touches
3 conflicts

0x49890ced…6f23

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 0x5a2290095e…d48e89

← previous block·next block →recent activity