← previous blocknext block →recent activity
Analyzing
Block #87,787,711
23 transactions · 21 stateful · 2026-07-14 22:16:03 UTC
Parallelism
52/100
Blocked
52%
Avg conflicts / tx
2.17
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #87,787,711 · 23 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w49w510w611w715w816w921w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9001f549…089d
0x34b655…2a6f
18 touches
36 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
16 touches
28 conflicts
0x5b145de0…367c
0xc8689a…ee79
12 touches
15 conflicts
0x22e7ebfe…1293
0x34b655…2a6f
12 touches
15 conflicts
0x28c62bca…b746
0x34b655…2a6f
12 touches
15 conflicts
0x58620f29…db5a
0x34b655…2a6f
12 touches
15 conflicts
0x9ae859db…2d84
0x34b655…2a6f
12 touches
15 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
36 conflicts on slot 0x9001f5497d…54089d
Audit this contract →
← previous block·next block →recent activity