← previous blocknext block →recent activity
Analyzing
Block #85,141,238
21 transactions · 17 stateful · 2026-07-02 15:43:11 UTC
Parallelism
81/100
Blocked
53%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,141,238 · 21 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
1w02w03w16w27w08w19w210w313w115w119w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x587911c7…9e01
0x34b655…2a6f
8 touches
6 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 conflicts
0x7c0bdc54…9dde
0x34b655…2a6f
6 touches
3 conflicts
0x9966da31…0d0f
0x34b655…2a6f
6 touches
3 conflicts
0xa1144aa9…7f67
0x34b655…2a6f
6 touches
3 conflicts
0xe732567d…b65d
0x34b655…2a6f
6 touches
3 conflicts
0xf3fbc9b8…ab58
0x34b655…2a6f
6 touches
3 conflicts
0xf7e59d30…11dd
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: Perpl
6 conflicts on slot 0x587911c74f…109e01
Audit this contract →
← previous block·next block →recent activity