← previous blocknext block →recent activity
Analyzing
Block #87,696,669
22 transactions · 20 stateful · 2026-07-14 12:06:35 UTC
Parallelism
73/100
Blocked
40%
Avg conflicts / tx
0.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,696,669 · 22 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
2w04w15w26w37w38w09w115w416w517w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0xe1ed670e…9e0b
0x34b655…2a6f
6 touches
3 conflicts
0xfdd655b8…bf89
0x34b655…2a6f
6 touches
3 conflicts
0x32dfa6a9…12f6
0x34b655…2a6f
4 touches
1 conflict
0x3e0072a8…95fc
0x34b655…2a6f
4 touches
1 conflict
0x41fc2b04…2805
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4c188934…158e
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity