← previous blocknext block →recent activity
Analyzing
Block #97,566,296
44 transactions · 38 stateful · 2026-08-20 07:30:11 UTC
Parallelism
70/100
Blocked
61%
Avg conflicts / tx
1.48
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #97,566,296 · 44 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w08w09w110w111w213w015w216w318w421w522w626w629w331w934w236w437w442w1243w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53a9defd…5bed
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x21ca7579…1a1e
0x34b655…2a6f
8 touches
6 conflicts
0x48b13e5e…3c2a
0x34b655…2a6f
8 touches
6 conflicts
0x326a02b5…8dad
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0x53a9defda6…ed5bed
Audit this contract →
← previous block·next block →recent activity