← previous blocknext block →recent activity
Analyzing
Block #97,820,134
24 transactions · 22 stateful · 2026-08-21 05:00:02 UTC
Parallelism
83/100
Blocked
41%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,820,134 · 24 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
3w04w15w06w17w18w212w013w015w116w119w020w121w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x921893c3…b9b6
0x34b655…2a6f
6 touches
3 conflicts
0x2407edc1…f2c8
0x34b655…2a6f
4 touches
1 conflict
0x3686cc89…4ffc
0xa6afd3…d132
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x7620a832…4ab4
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 0x921893c31c…45b9b6
Audit this contract →
← previous block·next block →recent activity