← previous blocknext block →recent activity
Analyzing
Block #87,662,253
20 transactions · 18 stateful · 2026-07-14 08:16:36 UTC
Parallelism
70/100
Blocked
44%
Avg conflicts / tx
0.75
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,662,253 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w08w29w110w312w413w118w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x20d1947c…4807
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xb125481e…4646
0x34b655…2a6f
6 touches
3 conflicts
0x1b2c54a1…5a76
0x34b655…2a6f
6 touches
3 conflicts
0x4cf39eee…2213
0x34b655…2a6f
4 touches
1 conflict
0x7d3c50c5…2279
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x91320c47…c941
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 0x20d1947ca1…584807
Audit this contract →
← previous block·next block →recent activity