← previous blocknext block →recent activity
Analyzing
Block #97,667,155
68 transactions · 49 stateful · 2026-08-20 16:05:09 UTC
Parallelism
65/100
Blocked
86%
Avg conflicts / tx
3.22
Longest chain
24 deep
Execution timeline
did this block parallelize well?
view
block #97,667,155 · 68 txs across 24 waves · depth 24
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
wave w18
wave w19
wave w20
wave w21
wave w22
wave w23
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w26w37w49w512w613w117w719w821w922w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
20 touches
45 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0xc824469a…6425
0x34b655…2a6f
20 touches
45 conflicts
0xcd2f4680…8684
0xd32edf…ff58
19 touches
45 conflicts
0x00000000…002c
0x1b6862…e19c
16 touches
28 conflicts
0xba5743c7…21c3
0x1b6862…e19c
16 touches
28 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…001c
0x1b6862…e19c
16 touches
28 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
45 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity