← previous blocknext block →recent activity
Analyzing
Block #86,905,164
16 transactions · 12 stateful · 2026-07-10 19:53:56 UTC
Parallelism
75/100
Blocked
42%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,905,164 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w29w310w011w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x7548b289…f0dc
0x34b655…2a6f
6 touches
3 conflicts
0x8dfef5ae…9361
0x34b655…2a6f
6 touches
3 conflicts
0xadd2210b…9e29
0x34b655…2a6f
6 touches
3 conflicts
0x247c7eb3…4428
0x34b655…2a6f
4 touches
1 conflict
0x36187d32…57e2
0x34b655…2a6f
4 touches
1 conflict
0xe60e9000…c058
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
6 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity