← previous blocknext block →recent activity

Analyzing

Block #86,987,397

23 transactions · 22 stateful · 2026-07-11 05:03:23 UTC

Parallelism

83/100

Blocked

36%

Avg conflicts / tx

0.57

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,987,397  ·  23 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

0x2858d6fd…0678

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x33bd5ec4…af53

0xa6afd3…d132

6 touches
3 conflicts

0xc7a15219…7745

0xa6afd3…d132

6 touches
3 conflicts

0x52e69143…95ad

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0002

0x04fdea…47d7

4 touches
1 conflict

0x13a54fa2…5ae3

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

6 conflicts on slot 0x2858d6fddc…d90678

← previous block·next block →recent activity