← previous blocknext block →recent activity
Analyzing
Block #97,566,479
21 transactions · 21 stateful · 2026-08-20 07:31:07 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,566,479 · 21 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
5w06w07w18w29w210w311w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
12 touches
15 conflicts
0x275ce6ab…730a
0x34b655…2a6f
8 touches
6 conflicts
0xf039e2f8…3d8a
0x34b655…2a6f
4 touches
1 conflict
0x101726f8…bf51
0x34b655…2a6f
4 touches
1 conflict
0x5e9ff235…8505
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb08c30c2…ee2b
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
15 conflicts on slot 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity