← previous blocknext block →recent activity
Analyzing
Block #97,558,319
40 transactions · 35 stateful · 2026-08-20 06:49:24 UTC
Parallelism
80/100
Blocked
66%
Avg conflicts / tx
1.3
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #97,558,319 · 40 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w07w18w29w310w412w514w015w116w228w330w139w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x103de0…bb55
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001a
0x1b6862…e19c
8 touches
6 conflicts
0xcc02d79e…7e86
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xce163d4f…b563
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
8 touches
6 conflicts
0xd5a25205…6459
0x1b6862…e19c
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: 0x103de0b5…25bb55
15 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity