← previous blocknext block →recent activity
Analyzing
Block #97,551,610
30 transactions · 27 stateful · 2026-08-20 06:15:02 UTC
Parallelism
87/100
Blocked
52%
Avg conflicts / tx
0.9
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,551,610 · 30 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
1w04w05w06w07w18w19w210w011w114w115w117w018w119w020w121w222w123w324w225w229w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x38c47502…1005
0x34b655…2a6f
6 touches
3 conflicts
0xf7bfb5fd…cb38
0x34b655…2a6f
6 touches
3 conflicts
0xe2457683…1957
0xa6afd3…d132
6 touches
3 conflicts
0xc0689428…8a2c
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
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
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity