← previous blocknext block →recent activity
Analyzing
Block #86,764,299
11 transactions · 10 stateful · 2026-07-10 04:12:21 UTC
Parallelism
73/100
Blocked
40%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,764,299 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w15w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee06e767…00d6
0x34b655…2a6f
6 touches
3 conflicts
0x6fe49da2…fd6f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xd72f309e…fa64
0x34b655…2a6f
6 touches
3 conflicts
0x17a7f697…dcb3
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
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 0xee06e76704…0e00d6
Audit this contract →
← previous block·next block →recent activity