← previous blocknext block →recent activity
Analyzing
Block #86,055,309
40 transactions · 31 stateful · 2026-07-06 21:14:01 UTC
Parallelism
73/100
Blocked
61%
Avg conflicts / tx
1.3
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #86,055,309 · 40 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w37w48w523w324w528w629w730w833w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
12 touches
15 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
12 touches
15 conflicts
0x76d1e78d…7877
0x40c49f…2af0
10 touches
10 conflicts
0x5d46e6a0…5ed9
0x40c49f…2af0
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x61377ba1…0bef
0xa6afd3…d132
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
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
15 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity