← previous blocknext block →recent activity
Analyzing
Block #87,910,335
18 transactions · 15 stateful · 2026-07-15 11:56:14 UTC
Parallelism
78/100
Blocked
33%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,910,335 · 18 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
1w02w17w08w19w010w111w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xe06bbb2e…9416
0x34b655…2a6f
4 touches
1 conflict
0xdb564c7f…72f9
0x34b655…2a6f
4 touches
1 conflict
0x884dd0f3…2af0
0x34b655…2a6f
4 touches
1 conflict
0x1e6e9104…f143
0x34b655…2a6f
4 touches
1 conflict
0xf47128a0…896a
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity