← previous blocknext block →recent activity

Analyzing

Block #88,092,344

21 transactions · 16 stateful · 2026-07-16 08:13:34 UTC

Parallelism

86/100

Blocked

44%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #88,092,344  ·  21 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xe41a6213…b1a6

0xd32edf…ff58

5 touches
3 conflicts

0x729c91b8…9537

0x188d58…ea8e

4 touches
1 conflict

0x729c91b8…9539

0x188d58…ea8e

4 touches
1 conflict

0x56a919c4…ab49

0xee8c0e…1242

4 touches
1 conflict

0x8a7af3fd…72a7

0x34b655…2a6f

4 touches
1 conflict

0xa03c2a35…52e6

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xcea1c853…7c30

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

3 conflicts on slot 0xe41a6213eb…ffb1a6

← previous block·next block →recent activity