← previous blocknext block →recent activity
Analyzing
Block #97,613,280
40 transactions · 34 stateful · 2026-08-20 11:28:03 UTC
Parallelism
57/100
Blocked
71%
Avg conflicts / tx
2.25
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #97,613,280 · 40 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
7w08w19w010w011w112w213w314w315w416w519w723w825w131w933w1038w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x17f192de…765e
0x34b655…2a6f
12 touches
15 conflicts
0x40ac662f…df77
0x34b655…2a6f
10 touches
10 conflicts
0x2e5cdd04…22ab
0x34b655…2a6f
8 touches
6 conflicts
0x47b2d2eb…8aa5
0x34b655…2a6f
8 touches
6 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0x88724b87…5e65
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity