← previous blocknext block →recent activity
Analyzing
Block #85,914,335
70 transactions · 53 stateful · 2026-07-06 05:32:52 UTC
Parallelism
80/100
Blocked
75%
Avg conflicts / tx
2.91
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #85,914,335 · 70 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w29w310w112w013w114w216w317w419w520w523w626w729w830w931w632w1052w1056w159w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x04fdea…47d7
24 touches
66 conflicts
0x66f473d3…2d03
0xa6afd3…d132
24 touches
66 conflicts
0x00000000…003d
0xa6afd3…d132
24 touches
66 conflicts
0x518f2037…e422
0xa6afd3…d132
22 touches
55 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
20 touches
45 conflicts
0x40970e69…da50
0x69df8a…6292
18 touches
36 conflicts
0x8cf3d245…1d0d
0x69df8a…6292
18 touches
36 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
18 touches
36 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: 0x04fdeac2…f747d7
66 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity