← previous blocknext block →recent activity
Analyzing
Block #97,683,141
22 transactions · 21 stateful · 2026-08-20 17:27:20 UTC
Parallelism
77/100
Blocked
43%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,683,141 · 22 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
1w03w05w06w17w18w211w212w313w115w119w020w121w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc56bb09e…9c88
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x69352f9f…5449
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x88b255be…0308
0xa6afd3…d132
4 touches
1 conflict
0x7f71827c…6bb9
0x065c9d…c394
4 touches
1 conflict
0x886db264…846e
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
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
6 conflicts on slot 0xc56bb09e4e…b79c88
Audit this contract →
← previous block·next block →recent activity