← previous blocknext block →recent activity
Analyzing
Block #87,588,073
21 transactions · 17 stateful · 2026-07-14 00:00:43 UTC
Parallelism
81/100
Blocked
35%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,588,073 · 21 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
6w07w18w09w010w113w214w115w318w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e86f6b3…99b7
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x1716b13d…99cc
0xc8689a…ee79
4 touches
1 conflict
0x94e0f6b9…3c85
0x34b655…2a6f
4 touches
1 conflict
0x97529895…5a02
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x034d14da…9f5f
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 0x4e86f6b3bc…d199b7
Audit this contract →
← previous block·next block →recent activity