← previous blocknext block →recent activity
Analyzing
Block #97,682,697
14 transactions · 14 stateful · 2026-08-20 17:25:05 UTC
Parallelism
79/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,682,697 · 14 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
1w03w04w15w16w28w210w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69352f9f…5449
0x34b655…2a6f
6 touches
3 conflicts
0x06e59321…0891
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xc56bb09e…9c88
0x34b655…2a6f
4 touches
1 conflict
0x24af1764…982d
0x34b655…2a6f
2 touches
0 conflicts
0x5566e17f…eb40
0x34b655…2a6f
2 touches
0 conflicts
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 0x69352f9f62…375449
Audit this contract →
← previous block·next block →recent activity