← previous blocknext block →recent activity
Analyzing
Block #97,397,132
20 transactions · 19 stateful · 2026-08-19 17:15:38 UTC
Parallelism
80/100
Blocked
32%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,397,132 · 20 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
1w05w06w17w08w111w113w214w319w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe221db26…080f
0x34b655…2a6f
8 touches
6 conflicts
0xd042b223…f61c
0x34b655…2a6f
8 touches
6 conflicts
0x5060cdde…445d
0x34b655…2a6f
4 touches
1 conflict
0x6f6aa736…a698
0x34b655…2a6f
4 touches
1 conflict
0x72c8aeb2…9921
0x34b655…2a6f
4 touches
1 conflict
0x85bfd0af…ce96
0x34b655…2a6f
4 touches
1 conflict
0x8ff85b19…dde0
0x34b655…2a6f
4 touches
1 conflict
0x947bb79d…6458
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 0xe221db26e8…ae080f
Audit this contract →
← previous block·next block →recent activity