← previous blocknext block →recent activity
Analyzing
Block #85,160,370
25 transactions · 25 stateful · 2026-07-02 17:50:34 UTC
Parallelism
80/100
Blocked
52%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,160,370 · 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
1w02w13w04w15w26w37w48w010w111w212w313w417w221w122w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x04fdea…47d7
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0xd0806a61…8350
0x34b655…2a6f
8 touches
6 conflicts
0x3149127f…19a9
0x34b655…2a6f
8 touches
6 conflicts
0x548145a9…cfce
0x34b655…2a6f
6 touches
3 conflicts
0x63b15849…80b2
0x34b655…2a6f
6 touches
3 conflicts
0xa1571d54…ae41
0x34b655…2a6f
6 touches
3 conflicts
0xaa35ced4…0724
0x34b655…2a6f
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: 0x04fdeac2…f747d7
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity