← previous blocknext block →recent activity

Analyzing

Block #87,753,066

23 transactions · 22 stateful · 2026-07-14 18:24:17 UTC

Parallelism

70/100

Blocked

32%

Avg conflicts / tx

0.78

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #87,753,066  ·  23 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

0xa2bc76f2…30df

0x34b655…2a6f

8 touches
6 conflicts

0xcc616f7f…6178

0x34b655…2a6f

8 touches
6 conflicts

0x33da0dfa…bac6

0x34b655…2a6f

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0x0733be30…112f

0x34b655…2a6f

8 touches
6 conflicts

0xa03dff75…cbf0

0x34b655…2a6f

6 touches
3 conflicts

0xa558e115…fc88

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

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: Perpl

6 conflicts on slot 0xa2bc76f2d3…2130df

← previous block·next block →recent activity