← previous blocknext block →recent activity
Analyzing
Block #97,611,963
20 transactions · 19 stateful · 2026-08-20 11:21:25 UTC
Parallelism
75/100
Blocked
53%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,611,963 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w08w19w210w111w212w313w414w116w017w119w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb7b446d2…2006
0x34b655…2a6f
6 touches
3 conflicts
0xcc9d4fca…ecbf
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x88724b87…5e65
0x34b655…2a6f
6 touches
3 conflicts
0x2e5cdd04…22ab
0x34b655…2a6f
4 touches
1 conflict
0x4786839b…c29a
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x625a0267…4ad6
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 0xb7b446d20b…4f2006
Audit this contract →
← previous block·next block →recent activity