← previous blocknext block →recent activity
Analyzing
Block #97,562,485
23 transactions · 21 stateful · 2026-08-20 07:10:43 UTC
Parallelism
83/100
Blocked
38%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,562,485 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w07w08w09w010w114w115w216w319w222w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x288a48ad…8275
0x34b655…2a6f
6 touches
3 conflicts
0x7fe7255a…8a7b
0x34b655…2a6f
6 touches
3 conflicts
0x4e58f1d6…2fca
0x34b655…2a6f
6 touches
3 conflicts
0xba407f5c…cc4a
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0x37699b20…1071
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
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
3 conflicts on slot 0x288a48adba…578275
Audit this contract →
← previous block·next block →recent activity