← previous blocknext block →recent activity
Analyzing
Block #97,501,291
23 transactions · 21 stateful · 2026-08-20 02:01:39 UTC
Parallelism
83/100
Blocked
38%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,501,291 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w07w08w19w112w213w315w216w322w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x655aa1bb…138c
0x40c49f…2af0
6 touches
3 conflicts
0xdcdeb4bd…903d
0x34b655…2a6f
6 touches
3 conflicts
0x1e0cf9b1…e924
0x40c49f…2af0
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x76ea4d0a…b4b6
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
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