← previous blocknext block →recent activity
Analyzing
Block #87,419,236
16 transactions · 14 stateful · 2026-07-13 05:10:51 UTC
Parallelism
69/100
Blocked
29%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,419,236 · 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
1w02w13w27w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e27bdfb…108a
0x34b655…2a6f
8 touches
6 conflicts
0xd2b44b36…b48d
0x34b655…2a6f
6 touches
3 conflicts
0x96bfa04d…d06b
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
6 touches
3 conflicts
0x587911c7…9e01
0x34b655…2a6f
4 touches
1 conflict
0x5e5e2711…cb2f
0x34b655…2a6f
4 touches
1 conflict
0x6c381064…bc43
0x34b655…2a6f
4 touches
1 conflict
0x7022f365…cd59
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 0x6e27bdfb04…5c108a
Audit this contract →
← previous block·next block →recent activity