← previous blocknext block →recent activity
Analyzing
Block #86,836,654
30 transactions · 27 stateful · 2026-07-10 12:15:52 UTC
Parallelism
67/100
Blocked
56%
Avg conflicts / tx
1.57
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #86,836,654 · 30 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w16w07w08w19w210w311w412w513w616w318w526w627w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0x8cc1393f…07fb
0x34b655…2a6f
10 touches
10 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x7da56943…9753
0x34b655…2a6f
6 touches
3 conflicts
0x85fed3a2…a604
0x34b655…2a6f
6 touches
3 conflicts
0x9f40a209…1193
0x34b655…2a6f
6 touches
3 conflicts
0xd8de9f79…53bd
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
21 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity