← previous blocknext block →recent activity
Analyzing
Block #87,584,407
27 transactions · 23 stateful · 2026-07-13 23:36:13 UTC
Parallelism
85/100
Blocked
39%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,584,407 · 27 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
1w03w14w05w16w07w112w013w115w219w220w321w124w025w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8252706a…7ca5
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x284bb696…4091
0x34b655…2a6f
4 touches
1 conflict
0x2e4e7336…e906
0x34b655…2a6f
4 touches
1 conflict
0x326d4924…1788
0x34b655…2a6f
4 touches
1 conflict
0x3ceeaf11…21a8
0x34b655…2a6f
4 touches
1 conflict
0x549e2d5d…d601
0x34b655…2a6f
4 touches
1 conflict
0x5f34fd08…aeb3
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: Perpl
6 conflicts on slot 0x8252706a8a…797ca5
Audit this contract →
← previous block·next block →recent activity