← previous blocknext block →recent activity
Analyzing
Block #97,825,253
21 transactions · 19 stateful · 2026-08-21 05:25:51 UTC
Parallelism
76/100
Blocked
47%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,825,253 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w19w010w112w213w215w016w217w319w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0x29be38f0…7bb1
0x40c49f…2af0
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xa149f0ce…4d65
0x40c49f…2af0
6 touches
3 conflicts
0xef4c5e68…1188
0x40c49f…2af0
6 touches
3 conflicts
0x3a921be0…779c
0x2a68ba…90c5
6 touches
3 conflicts
0xdde1e1b8…a9da
0x2b46c0…1669
4 touches
1 conflict
0xe49b1b9b…0be1
0x2b46c0…1669
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