← previous blocknext block →recent activity
Analyzing
Block #87,285,689
17 transactions · 16 stateful · 2026-07-12 14:17:44 UTC
Parallelism
71/100
Blocked
44%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,285,689 · 17 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
1w02w03w16w07w110w211w312w313w414w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38bdc5d3…a632
0x34b655…2a6f
6 touches
3 conflicts
0xd30f9e74…d404
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xbf78ee7f…e7fd
0x34b655…2a6f
6 touches
3 conflicts
0x7c09c53e…64b4
0x34b655…2a6f
4 touches
1 conflict
0x8212e232…180d
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 0x38bdc5d3e1…01a632
Audit this contract →
← previous block·next block →recent activity