← previous blocknext block →recent activity
Analyzing
Block #97,732,644
22 transactions · 21 stateful · 2026-08-20 21:38:25 UTC
Parallelism
77/100
Blocked
38%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,732,644 · 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
1w06w07w08w112w113w214w315w017w418w119w421w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8a29ec5…e823
0x34b655…2a6f
8 touches
6 conflicts
0x1bc9b1ca…85ef
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbec427fc…c56a
0x34b655…2a6f
4 touches
1 conflict
0xec2a8d79…70cb
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
6 conflicts on slot 0xe8a29ec5f9…32e823
Audit this contract →
← previous block·next block →recent activity