← previous blocknext block →recent activity
Analyzing
Block #87,737,964
25 transactions · 24 stateful · 2026-07-14 16:43:15 UTC
Parallelism
80/100
Blocked
50%
Avg conflicts / tx
0.96
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,737,964 · 25 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
1w04w05w16w27w38w412w013w115w116w217w319w220w323w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x3c0c2f32…c3df
0x34b655…2a6f
8 touches
6 conflicts
0x58620f29…db5a
0x34b655…2a6f
8 touches
6 conflicts
0x5b145de0…367c
0xc8689a…ee79
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x8d4c0bb9…ccd3
0x34b655…2a6f
8 touches
6 conflicts
0x9001f549…089d
0x34b655…2a6f
8 touches
6 conflicts
0xa45d24aa…1b77
0x34b655…2a6f
8 touches
6 conflicts
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity