← previous blocknext block →recent activity
Analyzing
Block #86,828,199
17 transactions · 14 stateful · 2026-07-10 11:19:21 UTC
Parallelism
65/100
Blocked
43%
Avg conflicts / tx
0.82
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,828,199 · 17 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
1w02w13w24w35w47w08w116w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3483ab79…8ed3
0x34b655…2a6f
10 touches
10 conflicts
0x9f40a209…1193
0x34b655…2a6f
10 touches
10 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x63c900f4…2600
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x922c7ebd…6600
0xc8689a…ee79
10 touches
10 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0x3483ab79f0…398ed3
Audit this contract →
← previous block·next block →recent activity