← previous blocknext block →recent activity
Analyzing
Block #86,747,503
25 transactions · 21 stateful · 2026-07-10 02:20:08 UTC
Parallelism
76/100
Blocked
38%
Avg conflicts / tx
0.72
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,747,503 · 25 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w19w013w214w316w022w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x157dbfb2…4089
0x34b655…2a6f
6 touches
3 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 conflicts
0x74550a4b…68bd
0x34b655…2a6f
6 touches
3 conflicts
0xa8b18ba0…f380
0x34b655…2a6f
6 touches
3 conflicts
0xb46ee126…a1a5
0x34b655…2a6f
6 touches
3 conflicts
0xb85b9f92…9a97
0x34b655…2a6f
6 touches
3 conflicts
0xd4f57998…3c18
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
6 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity