← previous blocknext block →recent activity
Analyzing
Block #87,730,384
18 transactions · 16 stateful · 2026-07-14 15:52:33 UTC
Parallelism
67/100
Blocked
31%
Avg conflicts / tx
0.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,730,384 · 18 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
3w04w16w27w311w012w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x87d20e73…1071
0x34b655…2a6f
6 touches
3 conflicts
0x0e2ca475…e91d
0x34b655…2a6f
4 touches
1 conflict
0x0fd87a64…6651
0x34b655…2a6f
4 touches
1 conflict
0x17d94c79…2463
0x34b655…2a6f
4 touches
1 conflict
0x1cdfe548…d3aa
0x34b655…2a6f
4 touches
1 conflict
0x259f167c…8dd7
0x34b655…2a6f
4 touches
1 conflict
0x31f6cdda…d22b
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity