← previous blocknext block →recent activity
Analyzing
Block #97,530,815
29 transactions · 22 stateful · 2026-08-20 04:30:11 UTC
Parallelism
90/100
Blocked
32%
Avg conflicts / tx
0.34
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,530,815 · 29 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
1w03w14w29w012w216w020w122w223w024w128w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2dcc0868…26bf
0x34b655…2a6f
6 touches
3 conflicts
0xd22915ae…11f6
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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 0x2dcc08681d…0026bf
Audit this contract →
← previous block·next block →recent activity