← previous blocknext block →recent activity
Analyzing
Block #99,356,416
24 transactions · 21 stateful · 2026-08-26 14:46:37 UTC
Parallelism
75/100
Blocked
48%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,356,416 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w07w18w29w210w311w012w116w117w218w319w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xa6d40b7f…2969
0x34b655…2a6f
10 touches
10 conflicts
0x52dfe1ab…4172
0x34b655…2a6f
6 touches
3 conflicts
0x6e3e9f18…f684
0x34b655…2a6f
6 touches
3 conflicts
0x27b6010e…e4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92f41d1f…4258
0xa6afd3…d132
4 touches
1 conflict
0x0de48c36…ef7a
0x34b655…2a6f
4 touches
1 conflict
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity