← previous blocknext block →recent activity
Analyzing
Block #86,775,753
13 transactions · 10 stateful · 2026-07-10 05:28:50 UTC
Parallelism
69/100
Blocked
40%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,775,753 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w08w29w310w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8258667b…b9ae
0x34b655…2a6f
6 touches
3 conflicts
0x04a428d1…4212
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x08398709…f32d
0x34b655…2a6f
4 touches
1 conflict
0x0c69433a…4f81
0x34b655…2a6f
4 touches
1 conflict
0x22bc4ea4…5c8a
0x34b655…2a6f
4 touches
1 conflict
0x4c214bb3…c5d3
0x34b655…2a6f
4 touches
1 conflict
0x567bb003…113a
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 0x8258667bf7…3db9ae
Audit this contract →
← previous block·next block →recent activity