← previous blocknext block →recent activity
Analyzing
Block #97,667,352
36 transactions · 36 stateful · 2026-08-20 16:06:11 UTC
Parallelism
61/100
Blocked
67%
Avg conflicts / tx
2.14
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #97,667,352 · 36 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
1w02w13w24w05w36w47w08w29w110w311w212w413w314w515w416w618w225w127w831w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
10 touches
10 conflicts
0xec7d120d…7084
0x34b655…2a6f
10 touches
10 conflicts
0x9db64d13…fb98
0x34b655…2a6f
10 touches
10 conflicts
0x2e40ce0b…9131
0xd32edf…ff58
9 touches
10 conflicts
0xba5743c7…21c3
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x22e0cc1d…ad0d
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity