← previous blocknext block →recent activity
Analyzing
Block #87,703,177
17 transactions · 14 stateful · 2026-07-14 12:50:18 UTC
Parallelism
76/100
Blocked
29%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,703,177 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w08w113w115w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65f01a9c…34e0
0x34b655…2a6f
8 touches
6 conflicts
0x93b6fab0…09d6
0x34b655…2a6f
6 touches
3 conflicts
0x16ba1d53…4480
0x34b655…2a6f
4 touches
1 conflict
0x1d826725…e975
0x34b655…2a6f
4 touches
1 conflict
0x3732c6c9…ded6
0x34b655…2a6f
4 touches
1 conflict
0x3a1edb3e…b841
0x34b655…2a6f
4 touches
1 conflict
0x3a37aad1…720f
0x34b655…2a6f
4 touches
1 conflict
0x683dbabb…acd8
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 0x65f01a9c4a…8b34e0
Audit this contract →
← previous block·next block →recent activity