← previous blocknext block →recent activity
Analyzing
Block #86,812,017
12 transactions · 10 stateful · 2026-07-10 09:30:58 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
0.83
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,812,017 · 12 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
3w04w16w27w38w310w011w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0xa37e64f8…ba05
0x34b655…2a6f
6 touches
3 conflicts
0xa436502e…edf6
0x34b655…2a6f
6 touches
3 conflicts
0xff90c737…13d2
0x34b655…2a6f
6 touches
3 conflicts
0xff90c737…13d3
0x34b655…2a6f
6 touches
3 conflicts
0x259f3ba0…a139
0x34b655…2a6f
4 touches
1 conflict
0xb06917e8…6985
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
6 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity