← previous blocknext block →recent activity
Analyzing
Block #99,090,071
59 transactions · 49 stateful · 2026-08-25 16:26:22 UTC
Parallelism
64/100
Blocked
76%
Avg conflicts / tx
3.83
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #99,090,071 · 59 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
1w02w13w04w18w09w110w211w312w413w528w140w341w443w645w749w1154w1657w19
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
36 touches
153 conflicts
0x889d5e90…929a
0x2a68ba…90c5
14 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0xa6afd3…d132
12 touches
15 conflicts
0x38963aeb…c33f
0xa6afd3…d132
12 touches
15 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
10 touches
10 conflicts
0x39773cec…38ed
0xa6afd3…d132
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 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: Perpl
153 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity