← previous blocknext block →recent activity
Analyzing
Block #97,604,824
32 transactions · 22 stateful · 2026-08-20 10:44:56 UTC
Parallelism
91/100
Blocked
50%
Avg conflicts / tx
0.47
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,604,824 · 32 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
1w02w13w14w29w013w114w115w216w017w019w021w022w124w225w129w131w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6aaacb4d…b18b
0x34b655…2a6f
6 touches
3 conflicts
0x21951d27…ae75
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0xd25997d0…a685
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 0x6aaacb4dd2…8fb18b
Audit this contract →
← previous block·next block →recent activity