← previous blocknext block →recent activity
Analyzing
Block #97,899,957
28 transactions · 21 stateful · 2026-08-21 11:49:23 UTC
Parallelism
86/100
Blocked
48%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,899,957 · 28 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
8w09w010w112w013w114w215w216w318w221w122w326w227w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0xdc9526ab…def7
0x40c49f…2af0
6 touches
3 conflicts
0x58138cee…d3d3
0x34b655…2a6f
4 touches
1 conflict
0x7151b1ad…4520
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x86bd79a5…1f48
0x34b655…2a6f
4 touches
1 conflict
0x8f84702c…c5f9
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity