← previous blocknext block →recent activity

Analyzing

Block #94,963,262

31 transactions · 28 stateful · 2026-08-11 04:14:12 UTC

Parallelism

68/100

Blocked

57%

Avg conflicts / tx

1.74

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #94,963,262  ·  31 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x2245baa9…a0e7

0xd32edf…ff58

19 touches
45 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xc7d7962f…3e04

0x34b655…2a6f

4 touches
1 conflict

0x2b5101ac…090b

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x850def09…120b

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

45 conflicts on slot 0x2245baa980…bda0e7

← previous block·next block →recent activity