← previous blocknext block →recent activity
Analyzing
Block #98,773,735
39 transactions · 34 stateful · 2026-08-24 13:48:05 UTC
Parallelism
59/100
Blocked
71%
Avg conflicts / tx
2.97
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #98,773,735 · 39 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
1w03w04w15w27w08w116w120w221w322w423w524w625w726w827w928w1029w1130w1231w1335w236w337w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
28 touches
91 conflicts
0x0d622e34…0000
0x681e90…ae09
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x5778d110…d2e6
0xc8689a…ee79
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x62910921…3016
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
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
91 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity