← previous blocknext block →recent activity
Analyzing
Block #97,841,612
18 transactions · 17 stateful · 2026-08-21 06:48:35 UTC
Parallelism
67/100
Blocked
41%
Avg conflicts / tx
0.72
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,841,612 · 18 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
2w03w15w07w18w29w310w112w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e27ac10…7251
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x2560b0ef…aadf
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…7213
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…7215
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…7223
0x34b655…2a6f
4 touches
1 conflict
0xadd5ff7c…8925
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 0x5e27ac10e5…e67251
Audit this contract →
← previous block·next block →recent activity