← previous blocknext block →recent activity
Analyzing
Block #97,726,294
49 transactions · 43 stateful · 2026-08-20 21:06:25 UTC
Parallelism
63/100
Blocked
72%
Avg conflicts / tx
2.61
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #97,726,294 · 49 txs across 18 waves · depth 18
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
wave w14
wave w15
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w05w210w011w112w213w321w723w824w928w829w930w1032w1143w1347w1748w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
12 touches
15 conflicts
0xec7d120d…7084
0x34b655…2a6f
10 touches
10 conflicts
0xc56bb09e…9c88
0x34b655…2a6f
10 touches
10 conflicts
0x78fb904c…7643
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity