← previous blocknext block →recent activity

Analyzing

Block #99,075,131

20 transactions · 19 stateful · 2026-08-25 15:10:53 UTC

Parallelism

75/100

Blocked

37%

Avg conflicts / tx

0.75

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #99,075,131  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x14e18cfe…d2ea

0xd32edf…ff58

9 touches
10 conflicts

0x46e2bb67…d8b3

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x62504564…1db8

0x34b655…2a6f

4 touches
1 conflict

0x7d6b9af1…9a38

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xb06a48e8…d6d1

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

10 conflicts on slot 0x14e18cfe6f…1ad2ea

← previous block·next block →recent activity