← previous blocknext block →recent activity
Analyzing
Block #86,915,340
16 transactions · 13 stateful · 2026-07-10 21:01:57 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,915,340 · 16 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
1w02w15w06w18w210w315w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x650e90b3…213d
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x11d3004e…e104
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xa4c4b591…7f9f
0x34b655…2a6f
6 touches
3 conflicts
0x650e90b3…213c
0x34b655…2a6f
6 touches
3 conflicts
0xe1ed670e…9e0b
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
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 0x650e90b3af…50213d
Audit this contract →
← previous block·next block →recent activity