← previous blocknext block →recent activity
Analyzing
Block #97,611,294
33 transactions · 24 stateful · 2026-08-20 11:18:03 UTC
Parallelism
91/100
Blocked
38%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,611,294 · 33 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
5w07w010w112w013w116w017w018w121w123w224w225w228w229w030w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5fc4192a…fe67
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x50e410ec…4bc7
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xcc4f1f14…aa5f
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
3 conflicts on slot 0x5fc4192a0a…effe67
Audit this contract →
← previous block·next block →recent activity