← previous blocknext block →recent activity
Analyzing
Block #87,053,989
13 transactions · 11 stateful · 2026-07-11 12:28:23 UTC
Parallelism
69/100
Blocked
27%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,053,989 · 13 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
5w07w08w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9199a85a…acd9
0x34b655…2a6f
8 touches
6 conflicts
0x56fed0dd…581f
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x56fed0dd…5820
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x8e672e7b…9c81
0x34b655…2a6f
6 touches
3 conflicts
0xa0092eae…c71c
0x34b655…2a6f
6 touches
3 conflicts
0x64d353bf…54ec
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 0x9199a85ae5…d3acd9
Audit this contract →
← previous block·next block →recent activity