← previous blocknext block →recent activity
Analyzing
Block #97,708,769
22 transactions · 21 stateful · 2026-08-20 19:37:40 UTC
Parallelism
73/100
Blocked
43%
Avg conflicts / tx
0.82
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,708,769 · 22 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
3w04w16w07w18w19w210w211w313w420w221w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ad9842a…1e2c
0x34b655…2a6f
6 touches
3 conflicts
0x9db64d13…fb98
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0x157b6348…8604
0x34b655…2a6f
6 touches
3 conflicts
0x48380858…c258
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
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 0x9ad9842a89…e11e2c
Audit this contract →
← previous block·next block →recent activity