← previous blocknext block →recent activity
Analyzing
Block #87,911,826
14 transactions · 13 stateful · 2026-07-15 12:06:12 UTC
Parallelism
71/100
Blocked
23%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,911,826 · 14 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
4w05w18w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcf5ef070…7d4f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0xa0ebadea…4145
0x34b655…2a6f
4 touches
1 conflict
0x60190970…1eb1
0x34b655…2a6f
4 touches
1 conflict
0x03bf1a82…9118
0x34b655…2a6f
4 touches
1 conflict
0x03bf1a82…9119
0x34b655…2a6f
4 touches
1 conflict
0xc36fa358…24cb
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 0xcf5ef07060…d87d4f
Audit this contract →
← previous block·next block →recent activity