← previous blocknext block →recent activity
Analyzing
Block #86,675,683
34 transactions · 30 stateful · 2026-07-09 18:20:30 UTC
Parallelism
62/100
Blocked
70%
Avg conflicts / tx
1.62
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #86,675,683 · 34 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w07w18w29w210w311w412w313w415w116w518w219w620w724w326w129w830w932w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56b5f5c0…a3ad
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1a9
0xb1dbf0…c0d3
8 touches
6 conflicts
0x8a35acfb…d1aa
0xb1dbf0…c0d3
8 touches
6 conflicts
0xb9b4eff6…c3ef
0x34b655…2a6f
6 touches
3 conflicts
0x4572c9a0…5cf9
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 0x56b5f5c03e…07a3ad
Audit this contract →
← previous block·next block →recent activity