← previous blocknext block →recent activity
Analyzing
Block #97,614,832
14 transactions · 12 stateful · 2026-08-20 11:35:51 UTC
Parallelism
57/100
Blocked
58%
Avg conflicts / tx
0.93
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,614,832 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w38w111w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa227f33f…c929
0x34b655…2a6f
6 touches
3 conflicts
0x66432bdc…57dc
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x21f66f20…fb49
0x34b655…2a6f
4 touches
1 conflict
0x27537d40…722e
0x34b655…2a6f
4 touches
1 conflict
0xe722a908…2b55
0x40c49f…2af0
4 touches
1 conflict
0x89845743…6ee0
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 0xa227f33f7e…87c929
Audit this contract →
← previous block·next block →recent activity