← previous blocknext block →recent activity
Analyzing
Block #97,990,522
21 transactions · 20 stateful · 2026-08-21 19:30:01 UTC
Parallelism
71/100
Blocked
55%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,990,522 · 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
1w02w03w05w06w17w28w39w010w111w212w113w014w116w318w419w520w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x4991b28b…99d6
0x34b655…2a6f
4 touches
1 conflict
0x4fa443a5…d07e
0x34b655…2a6f
4 touches
1 conflict
0x6254804c…a03c
0x34b655…2a6f
4 touches
1 conflict
0x705a9a1a…db08
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
3 conflicts on slot 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity