← previous blocknext block →recent activity
Analyzing
Block #87,579,171
22 transactions · 19 stateful · 2026-07-13 23:01:11 UTC
Parallelism
77/100
Blocked
37%
Avg conflicts / tx
0.82
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,579,171 · 22 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
1w02w16w09w010w011w112w213w114w219w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a5d321d…a474
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x2d651956…12e8
0x34b655…2a6f
6 touches
3 conflicts
0x503b3a72…f6df
0x34b655…2a6f
6 touches
3 conflicts
0x9fd372a1…a959
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x1c503794…b0da
0x34b655…2a6f
4 touches
1 conflict
0x1c796c6b…064e
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
10 conflicts on slot 0x1a5d321d5d…0da474
Audit this contract →
← previous block·next block →recent activity