← previous blocknext block →recent activity
Analyzing
Block #87,410,922
12 transactions · 10 stateful · 2026-07-13 04:15:16 UTC
Parallelism
67/100
Blocked
30%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,410,922 · 12 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
3w04w17w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x7c46fde6…d6a0
0x34b655…2a6f
6 touches
3 conflicts
0xdfd1344f…43f5
0x34b655…2a6f
4 touches
1 conflict
0x2211b188…0f6d
0x34b655…2a6f
4 touches
1 conflict
0x48e6f054…d2ac
0x34b655…2a6f
4 touches
1 conflict
0x63b98686…0a53
0x34b655…2a6f
4 touches
1 conflict
0x64a785e4…0110
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
6 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity