← previous blocknext block →recent activity
Analyzing
Block #97,396,006
21 transactions · 20 stateful · 2026-08-19 17:09:55 UTC
Parallelism
67/100
Blocked
35%
Avg conflicts / tx
0.95
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #97,396,006 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w16w07w28w310w413w519w620w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x3741a573…e309
0x34b655…2a6f
8 touches
6 conflicts
0x7de57974…f5ba
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xac2efe39…1f03
0x34b655…2a6f
5 touches
3 conflicts
0x89999c15…fdac
0x34b655…2a6f
4 touches
1 conflict
0xbfe333a4…687f
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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity