← previous blocknext block →recent activity
Analyzing
Block #85,982,966
28 transactions · 22 stateful · 2026-07-06 13:10:42 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
1.07
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #85,982,966 · 28 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w39w310w411w512w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
14 touches
21 conflicts
0xf5310ef7…485a
0x40c49f…2af0
10 touches
10 conflicts
0xd16df6cd…5532
0x40c49f…2af0
10 touches
10 conflicts
0x5f710177…d05b
0x40c49f…2af0
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x4e07169f…fd9a
0x40c49f…2af0
7 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xb72f2e06…5562
0x40c49f…2af0
5 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: 0x40c49f17…d22af0
21 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity