← previous blocknext block →recent activity
Analyzing
Block #87,691,158
14 transactions · 12 stateful · 2026-07-14 11:29:46 UTC
Parallelism
86/100
Blocked
25%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,691,158 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w17w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a625167…f20e
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x4b80417b…75c3
0x34b655…2a6f
4 touches
1 conflict
0x1ffbc5c9…461f
0x34b655…2a6f
2 touches
0 conflicts
0x282fd1fa…1fca
0x34b655…2a6f
2 touches
0 conflicts
0x59991669…58c6
0x34b655…2a6f
2 touches
0 conflicts
0xb7fa6bb8…32f8
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x1a62516791…64f20e
Audit this contract →
← previous block·next block →recent activity