← previous blocknext block →recent activity
Analyzing
Block #99,709,686
23 transactions · 21 stateful · 2026-08-27 20:33:51 UTC
Parallelism
74/100
Blocked
57%
Avg conflicts / tx
1.35
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,709,686 · 23 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
1w02w15w26w37w49w010w111w212w313w414w517w219w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0xa9d11061…b7e9
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xbbe6dd0b…a1bd
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x72411ea8…8b64
0x34b655…2a6f
4 touches
1 conflict
0xb8ef5aea…7dd5
0x065c9d…c394
3 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: Perpl
15 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity