← previous blocknext block →recent activity
Analyzing
Block #97,734,072
18 transactions · 18 stateful · 2026-08-20 21:45:36 UTC
Parallelism
67/100
Blocked
39%
Avg conflicts / tx
0.56
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,734,072 · 18 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
1w02w03w15w09w211w112w315w416w517w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x0bc43347…93d4
0x34b655…2a6f
6 touches
3 conflicts
0x72ec2001…6792
0x40c49f…2af0
4 touches
1 conflict
0x7bdccbcd…6bed
0x40c49f…2af0
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x0bc779a9…8644
0x34b655…2a6f
4 touches
1 conflict
0x3c22c08e…0099
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity