← previous blocknext block →recent activity
Analyzing
Block #85,193,863
16 transactions · 16 stateful · 2026-07-02 21:33:34 UTC
Parallelism
75/100
Blocked
25%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,193,863 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w010w111w112w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd63e616b…a07d
0x34b655…2a6f
6 touches
3 conflicts
0x1d351a9b…f2dd
0x34b655…2a6f
4 touches
1 conflict
0x32317ed6…85b0
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x765cd07a…1018
0x34b655…2a6f
4 touches
1 conflict
0xbcdaf37c…4cc4
0x34b655…2a6f
4 touches
1 conflict
0x4abbc09d…ddb0
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 0xd63e616b67…7fa07d
Audit this contract →
← previous block·next block →recent activity