← previous blocknext block →recent activity
Analyzing
Block #86,823,715
12 transactions · 11 stateful · 2026-07-10 10:49:22 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,823,715 · 12 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
3w06w17w29w310w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdba08802…6ba7
0x34b655…2a6f
6 touches
3 conflicts
0x16649a8b…40b0
0x34b655…2a6f
4 touches
1 conflict
0x16649a8b…40b1
0x34b655…2a6f
4 touches
1 conflict
0x28d4261c…56c7
0x34b655…2a6f
4 touches
1 conflict
0x3ee201fe…4802
0x34b655…2a6f
4 touches
1 conflict
0x5c37ca18…ffe0
0x34b655…2a6f
4 touches
1 conflict
0x5d7d3d99…cd99
0x34b655…2a6f
4 touches
1 conflict
0x6f7775d0…a8b4
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
3 conflicts on slot 0xdba08802ff…3e6ba7
Audit this contract →
← previous block·next block →recent activity