← previous blocknext block →recent activity
Analyzing
Block #97,510,839
27 transactions · 23 stateful · 2026-08-20 02:49:40 UTC
Parallelism
70/100
Blocked
48%
Avg conflicts / tx
1.33
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #97,510,839 · 27 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
2w05w06w08w19w212w314w415w518w625w726w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0x79e8f935…c3b6
0x34b655…2a6f
8 touches
6 conflicts
0x97d99bc6…2d86
0x34b655…2a6f
8 touches
6 conflicts
0x2dcc0868…26bf
0x34b655…2a6f
8 touches
6 conflicts
0x35c37635…11a6
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xba742940…9cdb
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity