← previous blocknext block →recent activity
Analyzing
Block #85,993,773
23 transactions · 18 stateful · 2026-07-06 14:22:59 UTC
Parallelism
74/100
Blocked
44%
Avg conflicts / tx
0.87
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,993,773 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w412w516w317w421w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5310ef7…485a
0x40c49f…2af0
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0xae5e6f9a…2991
0xc8689a…ee79
6 touches
3 conflicts
0x9fc8b97d…96da
0x2a68ba…90c5
6 touches
3 conflicts
0x213ee207…a151
0x69df8a…6292
6 touches
3 conflicts
0x46279ae7…20dd
0x69df8a…6292
6 touches
3 conflicts
0x53e50026…6d8c
0x69df8a…6292
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: 0x40c49f17…d22af0
10 conflicts on slot 0xf5310ef780…e2485a
Audit this contract →
← previous block·next block →recent activity