← previous blocknext block →recent activity
Analyzing
Block #99,329,351
94 transactions · 68 stateful · 2026-08-26 12:30:23 UTC
Parallelism
78/100
Blocked
81%
Avg conflicts / tx
4.01
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #99,329,351 · 94 txs across 21 waves · depth 21
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
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
wave w20
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w556w664w1265w1367w1469w1578w1686w687w788w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
42 touches
210 conflicts
0x889d5e90…929a
0x2a68ba…90c5
24 touches
66 conflicts
0xa9d7ad68…0003
0xd32edf…ff58
23 touches
66 conflicts
0x00000000…003d
0x40c49f…2af0
16 touches
28 conflicts
0x065ff70b…356d
0x40c49f…2af0
16 touches
28 conflicts
0x3f81bcfb…2905
0x40c49f…2af0
16 touches
28 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 conflicts
0x213ee207…a151
0x2b46c0…1669
14 touches
21 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: 0xf5b5f7f8…a36d70
210 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity