← previous blocknext block →recent activity
Analyzing
Block #87,640,729
25 transactions · 22 stateful · 2026-07-14 05:52:50 UTC
Parallelism
72/100
Blocked
32%
Avg conflicts / tx
0.76
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,640,729 · 25 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w19w010w111w212w013w015w317w423w524w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb670a63e…ead8
0x34b655…2a6f
8 touches
6 conflicts
0x25abfa46…5d5c
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x08330b36…ae29
0x34b655…2a6f
6 touches
3 conflicts
0x48028c31…6829
0x34b655…2a6f
4 touches
1 conflict
0x695fac15…263e
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0xb670a63ebd…04ead8
Audit this contract →
← previous block·next block →recent activity