← previous blocknext block →recent activity
Analyzing
Block #97,524,464
44 transactions · 38 stateful · 2026-08-20 03:58:14 UTC
Parallelism
68/100
Blocked
61%
Avg conflicts / tx
1.89
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #97,524,464 · 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
3w04w05w07w08w110w011w116w119w221w322w423w524w626w127w228w729w330w431w134w735w837w938w1039w1140w1241w1343w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0x107f84ba…8b0a
0x34b655…2a6f
8 touches
6 conflicts
0x2476d14a…cd78
0x34b655…2a6f
8 touches
6 conflicts
0x61f7bce8…3e84
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 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
28 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity