← previous blocknext block →recent activity
Analyzing
Block #99,494,217
54 transactions · 47 stateful · 2026-08-27 02:20:38 UTC
Parallelism
72/100
Blocked
68%
Avg conflicts / tx
2.69
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #99,494,217 · 54 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w110w011w112w015w117w218w319w020w022w126w129w230w332w433w436w237w141w542w345w646w747w848w950w1151w1253w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
24 touches
66 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
22 touches
55 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
20 touches
45 conflicts
0xb409e204…89ac
0x34b655…2a6f
12 touches
15 conflicts
0xf95715d3…c166
0x34b655…2a6f
8 touches
6 conflicts
0xbc28650c…7f05
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 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: Perpl
66 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity