← previous blocknext block →recent activity
Analyzing
Block #87,716,917
27 transactions · 23 stateful · 2026-07-14 14:22:28 UTC
Parallelism
85/100
Blocked
30%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,716,917 · 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
5w09w010w111w212w315w016w017w019w120w021w122w025w126w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xb11a3969…fc6a
0x34b655…2a6f
6 touches
3 conflicts
0xdfbd8991…5bd1
0x34b655…2a6f
6 touches
3 conflicts
0xe2f60be8…18bc
0x34b655…2a6f
6 touches
3 conflicts
0x343691dc…f5a8
0x34b655…2a6f
6 touches
3 conflicts
0x0ba865dd…a249
0x34b655…2a6f
6 touches
3 conflicts
0x74fd0a9b…3aaa
0x34b655…2a6f
6 touches
3 conflicts
0x7c0bdc54…9dde
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity