← previous blocknext block →recent activity
Analyzing
Block #97,603,303
23 transactions · 21 stateful · 2026-08-20 10:37:17 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,603,303 · 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
1w03w06w09w010w113w114w217w318w322w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a3068dd…18f1
0x34b655…2a6f
8 touches
6 conflicts
0xdbb2fff3…b122
0x34b655…2a6f
6 touches
3 conflicts
0xe2194a8c…e827
0x34b655…2a6f
6 touches
3 conflicts
0xdbb2fff3…b121
0x34b655…2a6f
6 touches
3 conflicts
0x6be37e18…14e1
0x34b655…2a6f
4 touches
1 conflict
0x80eee557…711d
0x34b655…2a6f
4 touches
1 conflict
0xaa0936a7…5a1d
0x34b655…2a6f
4 touches
1 conflict
0xbec23443…9293
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
6 conflicts on slot 0x9a3068dd84…9918f1
Audit this contract →
← previous block·next block →recent activity