← previous blocknext block →recent activity

Analyzing

Block #94,856,645

31 transactions · 24 stateful · 2026-08-10 19:17:58 UTC

Parallelism

77/100

Blocked

67%

Avg conflicts / tx

1.29

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #94,856,645  ·  31 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

0xdfe3731f…e93f

0xd32edf…ff58

13 touches
21 conflicts

0x9194f4a3…10b8

0x754704…b603

10 touches
10 conflicts

0x99f666e3…b2a2

0x3bd359…433a

10 touches
10 conflicts

0x00000000…0000

0xfa32f9…f3f0

10 touches
10 conflicts

0x00000000…0001

0xfa32f9…f3f0

10 touches
10 conflicts

0x8a2f9a36…fb4a

0xfa32f9…f3f0

8 touches
6 conflicts

0x13649b24…16e8

0x5dd8f3…c69c

6 touches
3 conflicts

0x0b552eae…fbd9

0x754704…b603

6 touches
3 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 0xdfe3731fba…e9e93f

← previous block·next block →recent activity