← previous blocknext block →recent activity
Analyzing
Block #97,666,294
45 transactions · 43 stateful · 2026-08-20 16:00:44 UTC
Parallelism
62/100
Blocked
72%
Avg conflicts / tx
2.22
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #97,666,294 · 45 txs across 17 waves · depth 17
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
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w25w36w18w09w010w111w212w213w314w315w416w422w724w927w1230w1532w436w137w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xb4a95e21…8ec7
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x753fbaca…6be4
0x34b655…2a6f
10 touches
10 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
10 touches
10 conflicts
0xae35966a…2b7e
0x34b655…2a6f
8 touches
6 conflicts
0xc4c059d8…185d
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
21 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity