← previous blocknext block →recent activity
Analyzing
Block #85,853,142
28 transactions · 23 stateful · 2026-07-05 22:45:23 UTC
Parallelism
82/100
Blocked
39%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,853,142 · 28 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w110w111w213w014w115w216w317w425w026w127w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe6f2ae57…2026
0x3bd359…433a
10 touches
10 conflicts
0xa472d565…9fe4
0x3bd359…433a
10 touches
10 conflicts
0x00000000…0003
0x431fed…d150
10 touches
10 conflicts
0x00000000…0002
0x431fed…d150
10 touches
10 conflicts
0x00000000…0000
0x431fed…d150
10 touches
10 conflicts
0x1ccfa324…0b93
0x0a917f…7777
10 touches
10 conflicts
0x44ad89ba…cf83
0x0a917f…7777
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
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: Wrapped MON (WMON)
10 conflicts on slot 0xe6f2ae5723…282026
Audit this contract →
← previous block·next block →recent activity