pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,611,882
← previous block
next block →
recent activity
Analyzing
Block #96,611,882
9 transactions · 9 stateful · 2026-08-16 22:42:38 UTC
Parallelism
67
/100
Blocked
33
%
Avg conflicts / tx
0.44
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,611,882
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrder
#2
execFwdPositionOpsV2
· blocks 1
#4
0x3f5c179b
· blocks 2
#7
0xed82b078
#8
setData
#3
execFwdPositionOpsV2
#5
0xed82b078
· blocks 1
#6
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1803586e…d149
0xa6afd3…d132
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x1e737223…2278
0x34b655…2a6f
2 touches
0 conflicts
0x25cdc19f…7efa
0x34b655…2a6f
2 touches
0 conflicts
0x33d7ab34…db37
0x34b655…2a6f
2 touches
0 conflicts
0x3d93ad2c…e747
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:
Kuru Exchange: Market-WETH/USDC
3 conflicts on slot
0x1803586e82…92d149
Audit this contract →
← previous block
·
next block →
recent activity