← previous blocknext block →recent activity

Analyzing

Block #107,847,704

27 transactions · 22 stateful · 2026-09-25 08:40:19 UTC

Parallelism

74/100

Blocked

64%

Avg conflicts / tx

1.33

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #107,847,704  ·  27 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

0x106e4de8…679d

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…0015

0x1b6862…e19c

10 touches
10 conflicts

0x90d24713…b88f

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

10 touches
10 conflicts

0x42522e76…2592

0x34b655…2a6f

8 touches
6 conflicts

0x3a663e9a…a9c4

0x508254…98bd

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x3a663e9a…a9c7

0x508254…98bd

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

21 conflicts on slot 0x106e4de8fd…c2679d

← previous block·next block →recent activity