← previous blocknext block →recent activity
Analyzing
Block #87,718,636
16 transactions · 14 stateful · 2026-07-14 14:33:58 UTC
Parallelism
63/100
Blocked
57%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,718,636 · 16 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
1w02w15w27w38w49w510w411w314w015w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6a1604d1…3e8a
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xa6c9a33e…d839
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x10ef891f…d725
0x34b655…2a6f
4 touches
1 conflict
0x10ef891f…d726
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x26bcd08c…8b42
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 0x6a1604d1a5…053e8a
Audit this contract →
← previous block·next block →recent activity