← previous blocknext block →recent activity
Analyzing
Block #87,715,068
21 transactions · 17 stateful · 2026-07-14 14:09:58 UTC
Parallelism
81/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,715,068 · 21 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
1w02w17w08w19w212w015w317w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x8a705be8…7ac4
0xc8689a…ee79
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x925dfa51…2cba
0x34b655…2a6f
4 touches
1 conflict
0xbe9baf16…df37
0x34b655…2a6f
4 touches
1 conflict
0xc30f2923…382c
0x34b655…2a6f
4 touches
1 conflict
0xe3f2706b…d3ec
0x34b655…2a6f
4 touches
1 conflict
0xfadc118d…5d64
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
3 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity