← previous blocknext block →recent activity

Analyzing

Block #95,372,010

23 transactions · 21 stateful · 2026-08-12 14:42:57 UTC

Parallelism

83/100

Blocked

33%

Avg conflicts / tx

0.48

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #95,372,010  ·  23 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

0x13db2ff4…c1b6

0xd32edf…ff58

7 touches
6 conflicts

0x261cbea7…e35e

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x04f6d949…d859

0x34b655…2a6f

4 touches
1 conflict

0x3439dfbc…0d03

0x34b655…2a6f

4 touches
1 conflict

0x4efae872…6aa8

0x34b655…2a6f

4 touches
1 conflict

0x8925be8e…4b81

0x34b655…2a6f

4 touches
1 conflict

0xacd1b162…bee6

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 0x13db2ff474…fbc1b6

← previous block·next block →recent activity