← previous blocknext block →recent activity
Analyzing
Block #86,988,356
18 transactions · 17 stateful · 2026-07-11 05:09:49 UTC
Parallelism
72/100
Blocked
29%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,988,356 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w18w011w113w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6ed530c…d450
0x34b655…2a6f
6 touches
3 conflicts
0x17cd796d…2afb
0x34b655…2a6f
4 touches
1 conflict
0x36638a70…343b
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6122676a…1970
0x34b655…2a6f
4 touches
1 conflict
0x6122676a…1971
0x34b655…2a6f
4 touches
1 conflict
0x6b267bdf…b173
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
3 conflicts on slot 0xb6ed530c56…eed450
Audit this contract →
← previous block·next block →recent activity