← previous blocknext block →recent activity
Analyzing
Block #97,562,640
18 transactions · 17 stateful · 2026-08-20 07:11:33 UTC
Parallelism
83/100
Blocked
41%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,562,640 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w07w08w110w111w216w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16dccb2b…170c
0x34b655…2a6f
6 touches
3 conflicts
0xae286b80…d5f3
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0x07b5c6c6…8865
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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 0x16dccb2b5a…e2170c
Audit this contract →
← previous block·next block →recent activity