← previous blocknext block →recent activity
Analyzing
Block #96,567,927
20 transactions · 19 stateful · 2026-08-16 19:01:32 UTC
Parallelism
75/100
Blocked
58%
Avg conflicts / tx
1.05
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,567,927 · 20 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
1w03w15w26w07w18w29w310w411w012w113w214w117w318w019w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x103de0…bb55
10 touches
10 conflicts
0x0313aedc…bfaf
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x38762f0b…11b9
0x065c9d…c394
5 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x3cb4a884…0d69
0x065c9d…c394
4 touches
1 conflict
0x9ff176a9…152e
0x065c9d…c394
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: 0x103de0b5…25bb55
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity