← previous blocknext block →recent activity
Analyzing
Block #97,568,364
28 transactions · 24 stateful · 2026-08-20 07:40:42 UTC
Parallelism
82/100
Blocked
42%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,568,364 · 28 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w08w09w114w015w016w217w118w319w120w121w222w126w427w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xea1d91a3…b583
0x34b655…2a6f
6 touches
3 conflicts
0xe2457683…1957
0xa6afd3…d132
6 touches
3 conflicts
0x44eba5d7…2ed2
0x34b655…2a6f
6 touches
3 conflicts
0xbec23443…9293
0x34b655…2a6f
4 touches
1 conflict
0xbec23443…9294
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity