← previous blocknext block →recent activity
Analyzing
Block #86,915,414
14 transactions · 8 stateful · 2026-07-10 21:02:26 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,915,414 · 14 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
7w09w111w213w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x11d3004e…e104
0x34b655…2a6f
6 touches
3 conflicts
0xa4c4b591…7f9f
0x34b655…2a6f
4 touches
1 conflict
0xb06917e8…6985
0x34b655…2a6f
4 touches
1 conflict
0xe60e9000…c058
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x1941b441…5889
0x34b655…2a6f
4 touches
1 conflict
0x650e90b3…213d
0x34b655…2a6f
4 touches
1 conflict
0x650e90b3…213c
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 0x11d3004e72…4fe104
Audit this contract →
← previous block·next block →recent activity