← previous blocknext block →recent activity
Analyzing
Block #85,817,071
36 transactions · 27 stateful · 2026-07-05 18:44:58 UTC
Parallelism
83/100
Blocked
41%
Avg conflicts / tx
0.42
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,817,071 · 36 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
1w02w13w27w110w311w412w515w216w024w128w229w033w134w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x033cf007…136d
0x34b655…2a6f
6 touches
3 conflicts
0x08943ea2…ed03
0x754704…b603
6 touches
3 conflicts
0x8a90e3e2…2a12
0x40c49f…2af0
6 touches
3 conflicts
0xc5eed2a9…545f
0xd32edf…ff58
5 touches
3 conflicts
0x342fbbca…d443
0x40c49f…2af0
4 touches
1 conflict
0xf6cc7de8…0b4a
0x3bd359…433a
4 touches
1 conflict
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity