← previous blocknext block →recent activity
Analyzing
Block #85,175,316
21 transactions · 20 stateful · 2026-07-02 19:30:02 UTC
Parallelism
86/100
Blocked
20%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,175,316 · 21 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
5w06w17w212w013w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x70638c24…1553
0x34b655…2a6f
6 touches
3 conflicts
0xc1aad6e5…9135
0x34b655…2a6f
6 touches
3 conflicts
0xb699771f…0907
0x34b655…2a6f
6 touches
3 conflicts
0x51a914cf…a822
0x34b655…2a6f
4 touches
1 conflict
0x6871c38d…d661
0x34b655…2a6f
4 touches
1 conflict
0x74fd0a9b…3aaa
0x34b655…2a6f
4 touches
1 conflict
0x8d4c0bb9…ccd3
0x34b655…2a6f
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity