← previous blocknext block →recent activity
Analyzing
Block #86,776,558
17 transactions · 16 stateful · 2026-07-10 05:34:12 UTC
Parallelism
76/100
Blocked
31%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,776,558 · 17 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
1w02w13w28w09w110w211w3
- 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
6 touches
3 conflicts
0xb34207f2…50c8
0xd32edf…ff58
5 touches
3 conflicts
0x0fedf54f…57fc
0x34b655…2a6f
4 touches
1 conflict
0x25f0d803…174f
0x34b655…2a6f
4 touches
1 conflict
0x25f0d803…174e
0x34b655…2a6f
4 touches
1 conflict
0x44485f70…b1ac
0x34b655…2a6f
4 touches
1 conflict
0x73a951a2…53db
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