← previous blocknext block →recent activity

Analyzing

Block #94,847,341

20 transactions · 17 stateful · 2026-08-10 18:31:10 UTC

Parallelism

65/100

Blocked

53%

Avg conflicts / tx

1.25

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #94,847,341  ·  20 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

0xe7a28b3d…4a5c

0xd32edf…ff58

13 touches
21 conflicts

0x0a0cecef…4ed0

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x840d3ab7…c8c4

0x34b655…2a6f

4 touches
1 conflict

0x3cf50d44…961b

0x34b655…2a6f

4 touches
1 conflict

0x021df0f6…5d6f

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

2 touches
0 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 0xe7a28b3d1b…8a4a5c

← previous block·next block →recent activity