← previous blocknext block →recent activity
Analyzing
Block #97,370,524
20 transactions · 19 stateful · 2026-08-19 14:40:43 UTC
Parallelism
60/100
Blocked
42%
Avg conflicts / tx
1.85
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #97,370,524 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w27w38w410w513w518w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x0bcbbcad…fc9c
0x34b655…2a6f
12 touches
15 conflicts
0xae520586…087f
0x34b655…2a6f
8 touches
6 conflicts
0x9c3ae274…e96a
0x34b655…2a6f
6 touches
3 conflicts
0x4360b49f…140d
0x34b655…2a6f
6 touches
3 conflicts
0x65398157…785c
0x34b655…2a6f
6 touches
3 conflicts
0x70f537e8…399b
0x34b655…2a6f
6 touches
3 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
28 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity