← previous blocknext block →recent activity
Analyzing
Block #87,640,231
18 transactions · 14 stateful · 2026-07-14 05:49:31 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,640,231 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w111w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53f393fa…00b9
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x89a63bb6…c2b5
0x34b655…2a6f
4 touches
1 conflict
0x99bc8b1a…2c66
0x34b655…2a6f
4 touches
1 conflict
0xaec6ac00…1bd7
0x34b655…2a6f
4 touches
1 conflict
0xcdd32c46…e107
0x34b655…2a6f
4 touches
1 conflict
0xe09e6d85…2f72
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 0x53f393fafd…2a00b9
Audit this contract →
← previous block·next block →recent activity