← previous blocknext block →recent activity
Analyzing
Block #86,851,190
25 transactions · 18 stateful · 2026-07-10 13:52:57 UTC
Parallelism
80/100
Blocked
44%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,851,190 · 25 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
4w05w16w27w38w411w212w016w317w423w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0xc6b9bb4b…145a
0x34b655…2a6f
8 touches
6 conflicts
0x3483ab79…8ed3
0x34b655…2a6f
6 touches
3 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 conflicts
0x32c56a67…5a47
0x34b655…2a6f
6 touches
3 conflicts
0x93e0900d…a837
0x34b655…2a6f
6 touches
3 conflicts
0x963816f5…b3fc
0x34b655…2a6f
6 touches
3 conflicts
0x9f40a209…1193
0x34b655…2a6f
6 touches
3 conflicts
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
10 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity