← previous blocknext block →recent activity
Analyzing
Block #86,785,911
17 transactions · 9 stateful · 2026-07-10 06:36:34 UTC
Parallelism
76/100
Blocked
44%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,785,911 · 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
4w06w19w115w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf60062ab…f98d
0x34b655…2a6f
4 touches
1 conflict
0x119694b6…b8dc
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xa92a015e…1934
0x34b655…2a6f
4 touches
1 conflict
0xb4ad3e17…76f4
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
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
1 conflict on slot 0xf60062ab4e…aef98d
Audit this contract →
← previous block·next block →recent activity