← previous blocknext block →recent activity
Analyzing
Block #86,708,954
23 transactions · 20 stateful · 2026-07-09 22:02:29 UTC
Parallelism
78/100
Blocked
40%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,708,954 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w05w16w07w19w010w111w212w316w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1a5
0xb1dbf0…c0d3
7 touches
6 conflicts
0x8a35acfb…d1a6
0xb1dbf0…c0d3
7 touches
6 conflicts
0x6c68ddc9…d106
0xb1dbf0…c0d3
6 touches
3 conflicts
0x3483ab79…8ed3
0x34b655…2a6f
6 touches
3 conflicts
0x7f430e47…4cbd
0xb1dbf0…c0d3
6 touches
3 conflicts
0xd0ec9500…6194
0x34b655…2a6f
6 touches
3 conflicts
0x0178c2de…b37d
0xb1dbf0…c0d3
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity