← previous blocknext block →recent activity

Analyzing

Block #87,331,327

19 transactions · 19 stateful · 2026-07-12 19:22:54 UTC

Parallelism

79/100

Blocked

42%

Avg conflicts / tx

0.68

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,331,327  ·  19 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xc2a774d3…e364

0xd32edf…ff58

7 touches
6 conflicts

0xc36fa358…24cb

0x34b655…2a6f

6 touches
3 conflicts

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0xb7dbe79a…4499

0x34b655…2a6f

6 touches
3 conflicts

0x1d84bebc…07d1

0x34b655…2a6f

4 touches
1 conflict

0x4e815ddc…2f85

0x34b655…2a6f

4 touches
1 conflict

0x680ca7d7…2df4

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

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

6 conflicts on slot 0xc2a774d397…fee364

← previous block·next block →recent activity