← previous blocknext block →recent activity
Analyzing
Block #86,774,266
19 transactions · 15 stateful · 2026-07-10 05:18:55 UTC
Parallelism
79/100
Blocked
47%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,774,266 · 19 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
1w02w15w06w19w210w011w312w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x74550a4b…68bd
0x34b655…2a6f
8 touches
6 conflicts
0x64a785e4…0110
0x34b655…2a6f
6 touches
3 conflicts
0x439484d9…2f92
0x34b655…2a6f
4 touches
1 conflict
0x4e782273…1690
0x34b655…2a6f
4 touches
1 conflict
0x7ae195ed…3632
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xaafa5115…10f7
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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 0x74550a4bea…1f68bd
Audit this contract →
← previous block·next block →recent activity