← previous blocknext block →recent activity
Analyzing
Block #97,544,815
41 transactions · 38 stateful · 2026-08-20 05:40:36 UTC
Parallelism
59/100
Blocked
68%
Avg conflicts / tx
2.66
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #97,544,815 · 41 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w08w010w011w115w218w321w523w324w725w826w927w1028w1131w132w134w240w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5cfec795…7c0e
0x34b655…2a6f
14 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0xec7d120d…7084
0x34b655…2a6f
12 touches
15 conflicts
0x0304ed8a…9f25
0x34b655…2a6f
10 touches
10 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
10 touches
10 conflicts
0xea1d91a3…b583
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x8902ba1f…f4b6
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
21 conflicts on slot 0x5cfec7957f…867c0e
Audit this contract →
← previous block·next block →recent activity