← previous blocknext block →recent activity
Analyzing
Block #97,383,854
23 transactions · 17 stateful · 2026-08-19 15:49:53 UTC
Parallelism
87/100
Blocked
35%
Avg conflicts / tx
0.35
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,383,854 · 23 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
2w03w14w212w017w118w219w020w121w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x367b69ad…33d8
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xc1c4518a…52c5
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0x367b69ad…33d9
0x34b655…2a6f
6 touches
3 conflicts
0x3b35a335…e934
0xd32edf…ff58
5 touches
3 conflicts
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x4a5956ef…e226
0x34b655…2a6f
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 0x367b69ad60…4333d8
Audit this contract →
← previous block·next block →recent activity