← previous blocknext block →recent activity
Analyzing
Block #97,989,829
19 transactions · 19 stateful · 2026-08-21 19:26:31 UTC
Parallelism
68/100
Blocked
58%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,989,829 · 19 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
1w02w03w04w15w17w08w19w010w111w112w213w314w315w416w518w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcaa5e459…c7eb
0x34b655…2a6f
10 touches
10 conflicts
0xdcebaf0d…ee40
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xbae5b1aa…2722
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x317be25c…54ec
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…1266
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
10 conflicts on slot 0xcaa5e45985…ccc7eb
Audit this contract →
← previous block·next block →recent activity