← previous blocknext block →recent activity
Analyzing
Block #86,916,221
17 transactions · 15 stateful · 2026-07-10 21:07:50 UTC
Parallelism
88/100
Blocked
7%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,916,221 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaf34ae1c…04db
0x34b655…2a6f
4 touches
1 conflict
0xcbe18c62…3a5c
0x34b655…2a6f
4 touches
1 conflict
0xcbe18c62…3a5d
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7ee6007b…fd68
0x34b655…2a6f
2 touches
0 conflicts
0x98d58911…19f2
0x34b655…2a6f
2 touches
0 conflicts
0xaa48195d…ffee
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0xaf34ae1c36…6004db
Audit this contract →
← previous block·next block →recent activity