← previous blocknext block →recent activity
Analyzing
Block #85,602,753
22 transactions · 21 stateful · 2026-07-04 18:56:45 UTC
Parallelism
86/100
Blocked
29%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,602,753 · 22 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
1w02w03w14w05w16w27w217w018w119w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc4e19ae4…0788
0xe7cd86…c82d
6 touches
3 conflicts
0xeaced15b…2221
0x754704…b603
6 touches
3 conflicts
0x6b0ceba5…f462
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x4848cef8…a1cb
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x33bd5ec4…af53
0xa6afd3…d132
4 touches
1 conflict
0xc7a15219…7745
0xa6afd3…d132
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: 0xe7cd86e1…0fc82d
3 conflicts on slot 0xc4e19ae47e…dc0788
Audit this contract →
← previous block·next block →recent activity