← previous blocknext block →recent activity
Analyzing
Block #87,622,207
16 transactions · 16 stateful · 2026-07-14 03:48:58 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,622,207 · 16 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
1w02w13w04w16w07w18w211w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a2a5dd6…fef4
0x34b655…2a6f
6 touches
3 conflicts
0x66b3eda5…7c90
0x34b655…2a6f
6 touches
3 conflicts
0x79e62da8…efdc
0x34b655…2a6f
6 touches
3 conflicts
0x07f69062…03ec
0x34b655…2a6f
4 touches
1 conflict
0x099dde1a…3e64
0x34b655…2a6f
4 touches
1 conflict
0x09cd9841…d332
0x34b655…2a6f
4 touches
1 conflict
0x0dcb313d…7073
0x34b655…2a6f
4 touches
1 conflict
0x0dddee26…7ec8
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 0x8a2a5dd6b8…74fef4
Audit this contract →
← previous block·next block →recent activity