← previous blocknext block →recent activity
Analyzing
Block #87,329,922
19 transactions · 19 stateful · 2026-07-12 19:13:30 UTC
Parallelism
63/100
Blocked
53%
Avg conflicts / tx
1.63
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,329,922 · 19 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
1w02w03w14w25w38w29w310w111w416w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9f287382…28e5
0x34b655…2a6f
12 touches
15 conflicts
0xc0124edf…7d30
0x34b655…2a6f
10 touches
10 conflicts
0xdc8d4ee0…def3
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x6393203e…a0e3
0x34b655…2a6f
6 touches
3 conflicts
0x63b15849…80b2
0x34b655…2a6f
6 touches
3 conflicts
0x63c900f4…2600
0x34b655…2a6f
6 touches
3 conflicts
0x727fbce7…0c80
0x34b655…2a6f
6 touches
3 conflicts
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
15 conflicts on slot 0x9f287382ab…1228e5
Audit this contract →
← previous block·next block →recent activity