← previous blocknext block →recent activity
Analyzing
Block #97,666,646
37 transactions · 35 stateful · 2026-08-20 16:02:30 UTC
Parallelism
60/100
Blocked
63%
Avg conflicts / tx
1.95
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #97,666,646 · 37 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w29w010w011w212w313w314w415w416w517w518w620w721w823w1024w1126w128w1231w135w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeadc1ace…5fc3
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xabf57eb6…416d
0x34b655…2a6f
10 touches
10 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
10 touches
10 conflicts
0xb4a95e21…8ec7
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xec7d120d…7084
0x34b655…2a6f
8 touches
6 conflicts
0x1bc9b1ca…85ef
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 0xeadc1ace81…e35fc3
Audit this contract →
← previous block·next block →recent activity