← previous blocknext block →recent activity
Analyzing
Block #97,603,893
36 transactions · 31 stateful · 2026-08-20 10:40:15 UTC
Parallelism
72/100
Blocked
61%
Avg conflicts / tx
1.58
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #97,603,893 · 36 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w26w37w48w59w510w611w712w814w315w417w520w635w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
12 touches
15 conflicts
0xec7d120d…7084
0x34b655…2a6f
10 touches
10 conflicts
0xcc9d4fca…ecbf
0x34b655…2a6f
8 touches
6 conflicts
0xe6bc2705…d15b
0x34b655…2a6f
6 touches
3 conflicts
0xdbc578df…706a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
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
21 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity