← previous blocknext block →recent activity
Analyzing
Block #86,922,287
24 transactions · 20 stateful · 2026-07-10 21:48:21 UTC
Parallelism
88/100
Blocked
30%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,922,287 · 24 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
1w03w04w15w07w08w111w112w214w118w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe718f3c7…c376
0x34b655…2a6f
6 touches
3 conflicts
0xf06c2cf5…61bd
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x94ba9c4a…41d8
0x34b655…2a6f
4 touches
1 conflict
0xc7981744…932f
0x34b655…2a6f
4 touches
1 conflict
0xee28d8b5…bd37
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
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 0xe718f3c792…72c376
Audit this contract →
← previous block·next block →recent activity