← previous blocknext block →recent activity
Analyzing
Block #87,662,240
16 transactions · 13 stateful · 2026-07-14 08:16:31 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,662,240 · 16 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
4w05w16w27w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x20d1947c…4807
0x34b655…2a6f
6 touches
3 conflicts
0x91320c47…c941
0x34b655…2a6f
6 touches
3 conflicts
0x85c84f98…06d7
0x34b655…2a6f
4 touches
1 conflict
0x9f33005b…0042
0x34b655…2a6f
4 touches
1 conflict
0xb125481e…4646
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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
10 conflicts on slot 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity