← previous blocknext block →recent activity
Analyzing
Block #86,979,923
11 transactions · 10 stateful · 2026-07-11 04:13:26 UTC
Parallelism
55/100
Blocked
40%
Avg conflicts / tx
0.91
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,979,923 · 11 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
4w05w17w28w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x45c033be…0aad
0x34b655…2a6f
6 touches
3 conflicts
0x6c7e1952…d9c9
0x34b655…2a6f
6 touches
3 conflicts
0xfec3435f…4a72
0x34b655…2a6f
6 touches
3 conflicts
0x5ea6f0c6…4801
0x34b655…2a6f
4 touches
1 conflict
0x04c1c529…0ee1
0x34b655…2a6f
4 touches
1 conflict
0x884dd0f3…2af0
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
10 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity