← previous blocknext block →recent activity
Analyzing
Block #86,532,182
20 transactions · 19 stateful · 2026-07-09 02:18:32 UTC
Parallelism
80/100
Blocked
37%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,532,182 · 20 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
1w02w13w16w07w09w110w211w312w318w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x98862f54…62ca
0x34b655…2a6f
6 touches
3 conflicts
0xaf216042…c781
0x34b655…2a6f
5 touches
3 conflicts
0x3284d35d…74af
0x34b655…2a6f
4 touches
1 conflict
0x47861365…d699
0x34b655…2a6f
4 touches
1 conflict
0x6ed66d79…9482
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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
3 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity