← previous blocknext block →recent activity
Analyzing
Block #97,824,898
44 transactions · 42 stateful · 2026-08-21 05:24:04 UTC
Parallelism
68/100
Blocked
64%
Avg conflicts / tx
1.98
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #97,824,898 · 44 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w06w17w29w010w111w112w213w214w315w416w517w518w619w620w721w822w123w324w427w231w337w842w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec7d120d…7084
0x34b655…2a6f
14 touches
21 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xc149b87f…65fc
0x34b655…2a6f
8 touches
6 conflicts
0xaaa40a27…27cd
0x34b655…2a6f
6 touches
3 conflicts
0x892daf6e…48d8
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
21 conflicts on slot 0xec7d120df9…5d7084
Audit this contract →
← previous block·next block →recent activity