← previous blocknext block →recent activity
Analyzing
Block #97,613,761
38 transactions · 36 stateful · 2026-08-20 11:30:28 UTC
Parallelism
58/100
Blocked
69%
Avg conflicts / tx
2.53
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #97,613,761 · 38 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
1w02w13w27w08w19w110w211w212w313w315w417w518w619w720w822w923w927w1029w233w1134w1237w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
14 touches
21 conflicts
0xec7d120d…7084
0x34b655…2a6f
12 touches
15 conflicts
0xed9f23a7…1129
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6426
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x88724b87…5e65
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
28 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity