← previous blocknext block →recent activity
Analyzing
Block #99,359,197
36 transactions · 35 stateful · 2026-08-26 15:00:41 UTC
Parallelism
61/100
Blocked
66%
Avg conflicts / tx
2.36
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #99,359,197 · 36 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w06w17w28w19w210w011w112w213w114w316w217w319w421w522w625w129w730w831w932w1033w1134w1235w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xead15497…1dbe
0x34b655…2a6f
10 touches
10 conflicts
0x080c3a8a…3088
0x34b655…2a6f
8 touches
6 conflicts
0xb0a8e01c…d86c
0x34b655…2a6f
6 touches
3 conflicts
0xb5c7c6aa…fdba
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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
36 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity