← previous blocknext block →recent activity
Analyzing
Block #87,626,870
11 transactions · 11 stateful · 2026-07-14 04:20:10 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,626,870 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62cc9214…441b
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x84e7c382…48ae
0x34b655…2a6f
4 touches
1 conflict
0xdcf93b63…ae96
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x04f4909f…6357
0x34b655…2a6f
2 touches
0 conflicts
0x0caac81d…a6f7
0x34b655…2a6f
2 touches
0 conflicts
0x10fec71b…e12f
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x62cc92143d…c4441b
Audit this contract →
← previous block·next block →recent activity