← previous blocknext block →recent activity
Analyzing
Block #95,088,817
16 transactions · 16 stateful · 2026-08-11 14:46:33 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,088,817 · 16 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
2w03w14w05w16w27w310w011w112w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9f0b0dc…4827
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x23d51e55…82c2
0x34b655…2a6f
6 touches
3 conflicts
0xd30f9e74…d404
0x34b655…2a6f
6 touches
3 conflicts
0x0ddfdaf2…9e00
0x34b655…2a6f
6 touches
3 conflicts
0x7d0eaae2…60b7
0x34b655…2a6f
4 touches
1 conflict
0x8ff85b19…dde0
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: Perpl
3 conflicts on slot 0xb9f0b0dc52…ec4827
Audit this contract →
← previous block·next block →recent activity