← previous blocknext block →recent activity
Analyzing
Block #97,561,035
17 transactions · 16 stateful · 2026-08-20 07:03:19 UTC
Parallelism
71/100
Blocked
44%
Avg conflicts / tx
0.94
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,561,035 · 17 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
2w03w04w15w06w19w210w311w415w316w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6737ee07…9978
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xda1f3e2c…b73d
0x34b655…2a6f
6 touches
3 conflicts
0x793aa64d…b09c
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x28442dbe…a3f2
0x34b655…2a6f
5 touches
3 conflicts
0x76ea4d0a…b4b6
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 0x6737ee07d3…1e9978
Audit this contract →
← previous block·next block →recent activity