← previous blocknext block →recent activity
Analyzing
Block #97,671,075
18 transactions · 17 stateful · 2026-08-20 16:25:18 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,671,075 · 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
1w02w13w04w17w08w29w011w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x06e40499…165e
0x2b46c0…1669
4 touches
1 conflict
0x45f562b2…9294
0x2b46c0…1669
4 touches
1 conflict
0x48ed1159…abe9
0x2b46c0…1669
4 touches
1 conflict
0x8488f10f…9353
0x2b46c0…1669
4 touches
1 conflict
0x8488f10f…9354
0x2b46c0…1669
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity