← previous blocknext block →recent activity
Analyzing
Block #97,674,024
16 transactions · 16 stateful · 2026-08-20 16:40:38 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,674,024 · 16 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
1w02w05w06w17w19w210w211w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc0988d33…e5c6
0x34b655…2a6f
6 touches
3 conflicts
0x41be9e75…9773
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x04c5c873…dd0a
0xa6afd3…d132
4 touches
1 conflict
0x1570037c…955f
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 0xc0988d3373…01e5c6
Audit this contract →
← previous block·next block →recent activity