← previous blocknext block →recent activity
Analyzing
Block #95,031,767
18 transactions · 15 stateful · 2026-08-11 09:58:47 UTC
Parallelism
72/100
Blocked
47%
Avg conflicts / tx
0.72
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,031,767 · 18 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
2w03w14w25w36w37w411w413w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a2f9a36…fb4a
0xfa32f9…f3f0
8 touches
6 conflicts
0x99f666e3…b2a2
0x3bd359…433a
8 touches
6 conflicts
0x9194f4a3…10b8
0x754704…b603
8 touches
6 conflicts
0x00000000…0000
0xfa32f9…f3f0
8 touches
6 conflicts
0x00000000…0001
0xfa32f9…f3f0
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xa0d3faac…ae01
0x754704…b603
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: 0xfa32f9ec…fef3f0
6 conflicts on slot 0x8a2f9a362c…60fb4a
Audit this contract →
← previous block·next block →recent activity