← previous blocknext block →recent activity
Analyzing
Block #85,923,375
29 transactions · 14 stateful · 2026-07-06 06:33:05 UTC
Parallelism
83/100
Blocked
36%
Avg conflicts / tx
0.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,923,375 · 29 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
1w03w15w210w312w013w114w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…001a
0x74d80e…25d4
10 touches
10 conflicts
0x00000000…001c
0x74d80e…25d4
10 touches
10 conflicts
0x00000000…0022
0x74d80e…25d4
10 touches
10 conflicts
0x00000000…001b
0x74d80e…25d4
10 touches
10 conflicts
0x00000000…0002
0x74d80e…25d4
8 touches
6 conflicts
0x3c223c30…06e6
0x3bd359…433a
8 touches
6 conflicts
0x00000000…0005
0x74d80e…25d4
6 touches
3 conflicts
0x6aa3628d…2ea3
0x849831…5081
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: 0x74d80ee4…0b25d4
10 conflicts on slot 0x0000000000…00001a
Audit this contract →
← previous block·next block →recent activity