← previous blocknext block →recent activity
Analyzing
Block #97,740,560
11 transactions · 11 stateful · 2026-08-20 22:18:14 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.73
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,740,560 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w15w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f9b918b…212d
0x34b655…2a6f
6 touches
3 conflicts
0x280d1119…ee4d
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0xfae25437…e02f
0x34b655…2a6f
4 touches
1 conflict
0x178fe051…465a
0x34b655…2a6f
2 touches
0 conflicts
0x3732c6c9…ded6
0x34b655…2a6f
2 touches
0 conflicts
0x5ef25979…b185
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 0x0f9b918b6f…1d212d
Audit this contract →
← previous block·next block →recent activity