← previous blocknext block →recent activity
Analyzing
Block #97,824,819
45 transactions · 37 stateful · 2026-08-21 05:23:40 UTC
Parallelism
69/100
Blocked
70%
Avg conflicts / tx
1.4
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #97,824,819 · 45 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w17w28w09w110w111w212w317w218w219w320w421w422w523w524w625w729w833w1035w236w1138w244w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
10 touches
10 conflicts
0x44e7b8f0…96e9
0x34b655…2a6f
8 touches
6 conflicts
0x451e482b…7e7d
0x34b655…2a6f
8 touches
6 conflicts
0xec7d120d…7084
0x34b655…2a6f
8 touches
6 conflicts
0xaaa40a27…27cd
0x34b655…2a6f
8 touches
6 conflicts
0xc149b87f…65fc
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity