← previous blocknext block →recent activity
Analyzing
Block #97,497,405
20 transactions · 19 stateful · 2026-08-20 01:42:06 UTC
Parallelism
75/100
Blocked
37%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,497,405 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w38w212w413w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcf80e177…646c
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x4fc16b3f…e1b9
0x34b655…2a6f
6 touches
3 conflicts
0x8329c51e…4064
0x34b655…2a6f
4 touches
1 conflict
0x8329c51e…4065
0x34b655…2a6f
4 touches
1 conflict
0xa242e227…2e45
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
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
6 conflicts on slot 0xcf80e1776a…ee646c
Audit this contract →
← previous block·next block →recent activity