← previous blocknext block →recent activity

Analyzing

Block #105,626,261

26 transactions · 25 stateful · 2026-09-17 14:13:32 UTC

Parallelism

77/100

Blocked

60%

Avg conflicts / tx

1.46

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #105,626,261  ·  26 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

0x87682cb1…3ad6

0xd32edf…ff58

11 touches
15 conflicts

0xaad6be10…0801

0x2a68ba…90c5

10 touches
10 conflicts

0xca841faa…486a

0x34b655…2a6f

10 touches
10 conflicts

0xada193dc…5c7c

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0xb87af72a…aef6

0x2a68ba…90c5

6 touches
3 conflicts

0x06e40499…165e

0x34ae4d…3fc5

6 touches
3 conflicts

0xa605468c…1bfc

0x34ae4d…3fc5

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

15 conflicts on slot 0x87682cb1e4…143ad6

← previous block·next block →recent activity