← previous blocknext block →recent activity
Analyzing
Block #95,758,640
18 transactions · 17 stateful · 2026-08-13 23:10:17 UTC
Parallelism
78/100
Blocked
24%
Avg conflicts / tx
0.28
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,758,640 · 18 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
4w08w19w213w314w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc22a0c80…6c90
0x34b655…2a6f
6 touches
3 conflicts
0xdbd174e4…b6f8
0x34b655…2a6f
4 touches
1 conflict
0x4c619b7d…f4fa
0x34b655…2a6f
4 touches
1 conflict
0xcf56f0ed…55e8
0x34b655…2a6f
4 touches
1 conflict
0x6939e474…4256
0x34b655…2a6f
4 touches
1 conflict
0x9ca6fa7b…aeb3
0x34b655…2a6f
4 touches
1 conflict
0x0d488000…3831
0x34b655…2a6f
4 touches
1 conflict
0x4e135144…4167
0x34b655…2a6f
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: Perpl
3 conflicts on slot 0xc22a0c8052…406c90
Audit this contract →
← previous block·next block →recent activity