← previous blocknext block →recent activity
Analyzing
Block #99,039,194
36 transactions · 34 stateful · 2026-08-25 12:06:58 UTC
Parallelism
56/100
Blocked
74%
Avg conflicts / tx
2.89
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #99,039,194 · 36 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w36w47w58w69w110w212w117w718w119w822w927w1028w329w1132w1234w1435w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0x4c410cdc…96bb
0x34b655…2a6f
10 touches
10 conflicts
0x9a100e05…c541
0x34b655…2a6f
10 touches
10 conflicts
0xb36e09cb…3be4
0xd32edf…ff58
9 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
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
36 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity