← previous blocknext block →recent activity

Analyzing

Block #94,758,750

25 transactions · 22 stateful · 2026-08-10 11:05:30 UTC

Parallelism

72/100

Blocked

45%

Avg conflicts / tx

1.04

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #94,758,750  ·  25 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

0xb55610a9…375f

0xd32edf…ff58

13 touches
21 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x0e22f39d…b92b

0x34b655…2a6f

4 touches
1 conflict

0x4acc6dca…a868

0x34b655…2a6f

4 touches
1 conflict

0x9ff94a68…7ae8

0x34b655…2a6f

4 touches
1 conflict

0xa0584cc6…bc73

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…641f

0x34b655…2a6f

4 touches
1 conflict

0xd7e4217d…7c6b

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 0xb55610a9ab…26375f

← previous block·next block →recent activity