← previous blocknext block →recent activity

Analyzing

Block #95,710,268

20 transactions · 18 stateful · 2026-08-13 19:06:47 UTC

Parallelism

80/100

Blocked

39%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #95,710,268  ·  20 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xa5abef12…d60e

0xd32edf…ff58

7 touches
6 conflicts

0xe75ce681…ba5f

0x188d58…ea8e

4 touches
1 conflict

0xe75ce681…ba60

0x188d58…ea8e

4 touches
1 conflict

0x08636046…e60f

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x2ac796c1…5bbc

0x34b655…2a6f

4 touches
1 conflict

0x48050070…28ec

0x34b655…2a6f

4 touches
1 conflict

0x57be321f…fecc

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

6 conflicts on slot 0xa5abef12fd…e4d60e

← previous block·next block →recent activity