← previous blocknext block →recent activity
Analyzing
Block #85,993,991
25 transactions · 21 stateful · 2026-07-06 14:24:27 UTC
Parallelism
80/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,993,991 · 25 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
1w02w13w04w17w010w013w114w216w317w419w123w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0xd16df6cd…5532
0x40c49f…2af0
8 touches
6 conflicts
0xf5310ef7…485a
0x40c49f…2af0
6 touches
3 conflicts
0xf60fd3a9…bdd8
0x40c49f…2af0
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x44e32bc5…e40b
0x40c49f…2af0
4 touches
1 conflict
0x88745858…4b82
0x40c49f…2af0
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: 0x40c49f17…d22af0
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity