← previous blocknext block →recent activity
Analyzing
Block #97,843,829
23 transactions · 22 stateful · 2026-08-21 07:00:02 UTC
Parallelism
78/100
Blocked
41%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,843,829 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w27w08w09w112w113w214w317w018w121w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0x1ba33c52…2015
0x34b655…2a6f
6 touches
3 conflicts
0x07546527…7feb
0x34b655…2a6f
6 touches
3 conflicts
0x315e07b8…9823
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x3dff027b…e474
0x34b655…2a6f
4 touches
1 conflict
0x62f35fe1…a395
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0x7de579746e…f0f5ba
Audit this contract →
← previous block·next block →recent activity