← previous blocknext block →recent activity
Analyzing
Block #85,198,043
13 transactions · 13 stateful · 2026-07-02 22:01:26 UTC
Parallelism
77/100
Blocked
23%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,198,043 · 13 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
6w010w111w212w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfadc118d…5d64
0x34b655…2a6f
4 touches
1 conflict
0xfbabb02d…af07
0x34b655…2a6f
4 touches
1 conflict
0xb245fe36…d765
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0f068b13…fb19
0x34b655…2a6f
2 touches
0 conflicts
0x11bf224b…eafe
0x34b655…2a6f
2 touches
0 conflicts
0x139987ef…c080
0x34b655…2a6f
2 touches
0 conflicts
0x1435528b…a8ae
0x34b655…2a6f
2 touches
0 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: Perpl
1 conflict on slot 0xfadc118dc2…025d64
Audit this contract →
← previous block·next block →recent activity