← previous blocknext block →recent activity
Analyzing
Block #97,740,080
57 transactions · 47 stateful · 2026-08-20 22:15:49 UTC
Parallelism
81/100
Blocked
77%
Avg conflicts / tx
1.89
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #97,740,080 · 57 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w37w412w013w115w016w117w219w421w425w527w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f9b918b…212d
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xac2a0273…721b
0x34b655…2a6f
12 touches
15 conflicts
0x5dc30355…38a7
0xd32edf…ff58
11 touches
15 conflicts
0x737acb78…fce8
0x34b655…2a6f
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0x085aa6fe…4334
0x065c9d…c394
9 touches
10 conflicts
0xca841faa…486a
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
15 conflicts on slot 0x0f9b918b6f…1d212d
Audit this contract →
← previous block·next block →recent activity