← previous blocknext block →recent activity
Analyzing
Block #97,726,353
28 transactions · 23 stateful · 2026-08-20 21:06:43 UTC
Parallelism
89/100
Blocked
35%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,726,353 · 28 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w09w010w114w116w017w118w219w020w121w024w125w227w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcb21158b…f18d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2684a9bd…12fa
0x34b655…2a6f
4 touches
1 conflict
0x280d1119…ee4d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5e782d17…5317
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 0xcb21158b83…66f18d
Audit this contract →
← previous block·next block →recent activity