← previous blocknext block →recent activity
Analyzing
Block #95,976,224
23 transactions · 22 stateful · 2026-08-14 17:25:01 UTC
Parallelism
74/100
Blocked
32%
Avg conflicts / tx
0.7
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,976,224 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w28w19w310w413w517w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbdc80bf7…e947
0x34b655…2a6f
8 touches
6 conflicts
0x1a5d321d…a474
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xb0fbfa63…215c
0x34b655…2a6f
6 touches
3 conflicts
0xef048f92…572b
0x34b655…2a6f
4 touches
1 conflict
0x0192edef…ffdc
0x34b655…2a6f
4 touches
1 conflict
0x0b0611f7…e63a
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
6 conflicts on slot 0xbdc80bf733…aae947
Audit this contract →
← previous block·next block →recent activity