← previous blocknext block →recent activity
Analyzing
Block #96,029,684
21 transactions · 13 stateful · 2026-08-14 21:54:02 UTC
Parallelism
86/100
Blocked
38%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,029,684 · 21 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
4w06w17w29w012w116w217w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x0cd0ecae…f4b1
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x3464bbc5…a323
0xa6afd3…d132
4 touches
1 conflict
0xf219f7cf…7379
0xa6afd3…d132
4 touches
1 conflict
0x1a920eda…bfae
0x386489…7508
2 touches
0 conflicts
0x00000000…0036
0x39f901…6bdf
2 touches
0 conflicts
0xc5819118…1448
0x39f901…6bdf
2 touches
0 conflicts
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: Kuru Exchange: MarginAccount
3 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity