← previous blocknext block →recent activity
Analyzing
Block #86,804,069
21 transactions · 18 stateful · 2026-07-10 08:37:52 UTC
Parallelism
67/100
Blocked
39%
Avg conflicts / tx
0.81
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,804,069 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w311w415w519w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
12 touches
15 conflicts
0xfec3435f…4a72
0x34b655…2a6f
6 touches
3 conflicts
0xbbee202a…8912
0x34b655…2a6f
6 touches
3 conflicts
0xbbee202a…8913
0x34b655…2a6f
6 touches
3 conflicts
0xdfc58aa8…e1df
0x34b655…2a6f
6 touches
3 conflicts
0xdfd1344f…43f5
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
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
15 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity