← previous blocknext block →recent activity
Analyzing
Block #97,731,079
22 transactions · 18 stateful · 2026-08-20 21:30:33 UTC
Parallelism
64/100
Blocked
61%
Avg conflicts / tx
1.27
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #97,731,079 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w07w010w111w212w315w216w417w518w619w721w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5938cff…6608
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xfaab1754…53be
0x34b655…2a6f
8 touches
6 conflicts
0x6aa624fd…a850
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x92516a65…830e
0x34b655…2a6f
6 touches
3 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 0xf5938cffe7…806608
Audit this contract →
← previous block·next block →recent activity