← previous blocknext block →recent activity
Analyzing
Block #97,395,988
27 transactions · 24 stateful · 2026-08-19 17:09:50 UTC
Parallelism
78/100
Blocked
38%
Avg conflicts / tx
0.59
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,395,988 · 27 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w25w37w010w111w214w316w418w526w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x3a921be0…779c
0x2a68ba…90c5
6 touches
3 conflicts
0x111992a1…9894
0x40c49f…2af0
5 touches
3 conflicts
0x89aae15b…ea2e
0xd32edf…ff58
5 touches
3 conflicts
0xd042b223…f61c
0x34b655…2a6f
4 touches
1 conflict
0x135bc5bb…76c5
0x065c9d…c394
4 touches
1 conflict
0x48acfd83…7ef0
0x40c49f…2af0
4 touches
1 conflict
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: 0x40c49f17…d22af0
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity