← previous blocknext block →recent activity
Analyzing
Block #97,666,414
24 transactions · 23 stateful · 2026-08-20 16:01:20 UTC
Parallelism
75/100
Blocked
48%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,666,414 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w16w17w28w29w310w413w314w515w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x753fbaca…6be4
0x34b655…2a6f
10 touches
10 conflicts
0xec7d120d…7084
0x34b655…2a6f
8 touches
6 conflicts
0x40ac662f…df77
0x34b655…2a6f
8 touches
6 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x4e7eb462…b2ae
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x482471ad…122f
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 0x753fbaca2b…706be4
Audit this contract →
← previous block·next block →recent activity