← previous blocknext block →recent activity
Analyzing
Block #97,612,943
22 transactions · 20 stateful · 2026-08-20 11:26:21 UTC
Parallelism
77/100
Blocked
45%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,612,943 · 22 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
1w02w13w25w09w010w011w112w013w114w215w316w117w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x75a78ce6…e5d3
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x88724b87…5e65
0x34b655…2a6f
6 touches
3 conflicts
0x94610395…f8ee
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xdfa159d0…1576
0x065c9d…c394
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
6 conflicts on slot 0x75a78ce62c…bde5d3
Audit this contract →
← previous block·next block →recent activity