← previous blocknext block →recent activity
Analyzing
Block #86,979,904
14 transactions · 10 stateful · 2026-07-11 04:13:19 UTC
Parallelism
79/100
Blocked
30%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,979,904 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x6c7e1952…d9c9
0x34b655…2a6f
6 touches
3 conflicts
0x0ae9d2df…f788
0x34b655…2a6f
4 touches
1 conflict
0x0fedf54f…57fc
0x34b655…2a6f
4 touches
1 conflict
0x3c7908ed…47c8
0x34b655…2a6f
4 touches
1 conflict
0xb5c1ae56…437a
0x34b655…2a6f
4 touches
1 conflict
0xe25eabc5…56e6
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity