← previous blocknext block →recent activity
Analyzing
Block #87,663,559
14 transactions · 10 stateful · 2026-07-14 08:25:20 UTC
Parallelism
71/100
Blocked
40%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,663,559 · 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
4w06w17w28w310w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x0f15f74f…8d72
0x34b655…2a6f
4 touches
1 conflict
0x1737ef68…1e55
0x34b655…2a6f
4 touches
1 conflict
0x2392e78b…bf1d
0x34b655…2a6f
4 touches
1 conflict
0x799ee783…1f74
0x34b655…2a6f
4 touches
1 conflict
0x7e1d87b8…291c
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 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity