← previous blocknext block →recent activity

Analyzing

Block #93,188,975

26 transactions · 23 stateful · 2026-08-04 23:13:52 UTC

Parallelism

73/100

Blocked

57%

Avg conflicts / tx

1.27

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #93,188,975  ·  26 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

0x0a44bf23…9c25

0xd32edf…ff58

13 touches
21 conflicts

0x43121a72…4b1c

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x033cf007…136d

0x34b655…2a6f

6 touches
3 conflicts

0x7175a904…640c

0x34b655…2a6f

6 touches
3 conflicts

0xba5743c7…21c1

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

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 0x0a44bf23a9…df9c25

← previous block·next block →recent activity