← previous blocknext block →recent activity
Analyzing
Block #97,502,549
25 transactions · 22 stateful · 2026-08-20 02:07:58 UTC
Parallelism
88/100
Blocked
45%
Avg conflicts / tx
0.48
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,502,549 · 25 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w27w08w111w012w114w115w217w119w222w023w124w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x655aa1bb…138c
0x40c49f…2af0
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x45438ec1…0b54
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x16010ff0…233a
0x40c49f…2af0
4 touches
1 conflict
0x1e0cf9b1…e924
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
3 conflicts on slot 0x655aa1bbf9…03138c
Audit this contract →
← previous block·next block →recent activity