← previous blocknext block →recent activity
Analyzing
Block #86,958,928
16 transactions · 15 stateful · 2026-07-11 01:53:10 UTC
Parallelism
63/100
Blocked
40%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,958,928 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w08w39w411w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1ad
0xb1dbf0…c0d3
7 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x6c68ddc9…d106
0xb1dbf0…c0d3
5 touches
3 conflicts
0x8a35acfb…d1ae
0xb1dbf0…c0d3
5 touches
3 conflicts
0x5b37bb6b…ab00
0x34b655…2a6f
4 touches
1 conflict
0x67d02b69…3795
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity