← previous blocknext block →recent activity
Analyzing
Block #86,789,144
19 transactions · 17 stateful · 2026-07-10 06:58:10 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
1.21
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,789,144 · 19 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
1w06w07w18w29w310w412w113w514w617w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x698e3c53…a4c4
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x7d6e48e8…f2b5
0x34b655…2a6f
6 touches
3 conflicts
0x3c3621c7…3e11
0x34b655…2a6f
4 touches
1 conflict
0x4293a398…286e
0x34b655…2a6f
4 touches
1 conflict
0x4293a398…286f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0x698e3c537a…0da4c4
Audit this contract →
← previous block·next block →recent activity