← previous blocknext block →recent activity
Analyzing
Block #86,853,738
58 transactions · 51 stateful · 2026-07-10 14:10:01 UTC
Parallelism
64/100
Blocked
76%
Avg conflicts / tx
4.17
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #86,853,738 · 58 txs across 21 waves · depth 21
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
wave w20
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w17w28w49w510w638w539w742w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
34 touches
136 conflicts
0x4e3abeff…18eb
0x34b655…2a6f
20 touches
45 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
14 touches
21 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
12 touches
15 conflicts
0x3a192eef…3c7f
0x34b655…2a6f
12 touches
15 conflicts
0x4f4bdabd…ffba
0x34b655…2a6f
12 touches
15 conflicts
0xa07e7b13…7513
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 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
136 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity