← previous blocknext block →recent activity
Analyzing
Block #86,755,896
20 transactions · 17 stateful · 2026-07-10 03:16:17 UTC
Parallelism
75/100
Blocked
47%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,755,896 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w110w211w312w313w418w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34443913…cbf3
0x336ed4…c59c
6 touches
3 conflicts
0x47d4745e…02bb
0x336ed4…c59c
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…000a
0x90c374…be45
6 touches
3 conflicts
0x00000000…000b
0x90c374…be45
6 touches
3 conflicts
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: 0x336ed437…cfc59c
3 conflicts on slot 0x3444391364…9ecbf3
Audit this contract →
← previous block·next block →recent activity