← previous blocknext block →recent activity
Analyzing
Block #86,635,340
28 transactions · 24 stateful · 2026-07-09 13:49:49 UTC
Parallelism
82/100
Blocked
38%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,635,340 · 28 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
3w04w16w08w19w210w113w114w315w116w426w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xf93b4db1…f898
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x56153262…21ce
0x34b655…2a6f
6 touches
3 conflicts
0xada5ad75…1d24
0x34b655…2a6f
4 touches
2 conflicts
0x43bb28d7…7bd7
0x34b655…2a6f
4 touches
1 conflict
0x4c214bb3…c5d3
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity