← previous blocknext block →recent activity

Analyzing

Block #87,363,060

24 transactions · 23 stateful · 2026-07-12 22:55:03 UTC

Parallelism

71/100

Blocked

48%

Avg conflicts / tx

1.17

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #87,363,060  ·  24 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

0xdd207b65…d1e7

0xd32edf…ff58

11 touches
15 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x00000000…001e

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002e

0x1b6862…e19c

6 touches
3 conflicts

0x84611dd3…b347

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

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

15 conflicts on slot 0xdd207b6598…53d1e7

← previous block·next block →recent activity