← previous blocknext block →recent activity
Analyzing
Block #85,853,820
44 transactions · 27 stateful · 2026-07-05 22:49:51 UTC
Parallelism
89/100
Blocked
59%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,853,820 · 44 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
2w04w15w06w17w29w010w114w015w117w018w020w321w422w124w025w126w227w328w140w141w242w343w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdec5bfea…d17f
0xa6afd3…d132
8 touches
6 conflicts
0x44ad89ba…cf83
0x0a917f…7777
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xa472d565…9fe4
0x3bd359…433a
8 touches
6 conflicts
0xe6f2ae57…2026
0x3bd359…433a
8 touches
6 conflicts
0x00000000…0000
0x431fed…d150
8 touches
6 conflicts
0x00000000…0002
0x431fed…d150
8 touches
6 conflicts
0x00000000…0003
0x431fed…d150
8 touches
6 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: Kuru Exchange: Market-WETH/USDC
6 conflicts on slot 0xdec5bfea10…c4d17f
Audit this contract →
← previous block·next block →recent activity