← previous blocknext block →recent activity
Analyzing
Block #87,760,533
18 transactions · 18 stateful · 2026-07-14 19:14:12 UTC
Parallelism
72/100
Blocked
44%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,760,533 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w16w27w38w49w315w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x96d4f560…c558
0x34b655…2a6f
8 touches
6 conflicts
0xa0a5bed4…1d15
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0x162bea72…e9d1
0x34b655…2a6f
4 touches
1 conflict
0x367b69ad…33d9
0x34b655…2a6f
4 touches
1 conflict
0x36890fff…f3d1
0x34b655…2a6f
4 touches
1 conflict
0x520f8a31…65c5
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 0x96d4f560cd…75c558
Audit this contract →
← previous block·next block →recent activity