← previous blocknext block →recent activity
Analyzing
Block #86,059,177
28 transactions · 23 stateful · 2026-07-06 21:39:44 UTC
Parallelism
79/100
Blocked
61%
Avg conflicts / tx
1.04
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,059,177 · 28 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
2w03w04w15w26w37w08w19w210w312w017w218w319w320w421w524w125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
10 touches
10 conflicts
0x76d1e78d…7877
0x40c49f…2af0
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…0002
0x04fdea…47d7
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x5d46e6a0…5ed9
0x40c49f…2af0
6 touches
3 conflicts
0x5afa5804…8484
0x40c49f…2af0
5 touches
3 conflicts
0x46279ae7…20dd
0x69df8a…6292
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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity