← previous blocknext block →recent activity
Analyzing
Block #97,476,950
9 transactions · 9 stateful · 2026-08-19 23:59:12 UTC
Parallelism
56/100
Blocked
33%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,476,950 · 9 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x35c37635…11a6
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xe3684e08…c96a
0x34b655…2a6f
4 touches
1 conflict
0x2dcc0868…26bf
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x80398c66…f3cc
0x34b655…2a6f
4 touches
1 conflict
0x88e771e8…7d4a
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0x35c37635a4…5311a6
Audit this contract →
← previous block·next block →recent activity