← previous blocknext block →recent activity

Analyzing

Block #94,913,033

23 transactions · 18 stateful · 2026-08-11 00:01:33 UTC

Parallelism

70/100

Blocked

61%

Avg conflicts / tx

1.57

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #94,913,033  ·  23 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

0xe520175d…e0c1

0xd32edf…ff58

13 touches
21 conflicts

0xa1087a5c…66c4

0x754704…b603

12 touches
15 conflicts

0x11b69a7e…334e

0x01bff4…1071

6 touches
3 conflicts

0x0778475b…bd75

0x2a68ba…90c5

5 touches
3 conflicts

0x2bd6a53c…4d1f

0x065c9d…c394

4 touches
1 conflict

0x07b86c51…cdae

0x2a68ba…90c5

4 touches
1 conflict

0xf6cc7de8…0b4a

0x3bd359…433a

4 touches
1 conflict

0x00000000…0000

0x63e48b…53f2

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 0xe520175dcc…dde0c1

← previous block·next block →recent activity