pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,084,088
← previous block
next block →
recent activity
Analyzing
Block #96,084,088
13 transactions · 12 stateful · 2026-08-15 02:27:42 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,084,088
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0xab083028
#3
0x5acec890
#4
swap
#5
execFwdPositionOpsV2
#6
execFwdPositionOpsV2
#7
updatePosition
#8
0x3f5c179b
#9
execFwdPositionOpsV2
· blocks 1
#11
0x61c414…6698
#12
setData
#10
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4cabb80a…46bf
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0002
0x103de0…bb55
2 touches
0 conflicts
0x1d435609…eaa9
0x34b655…2a6f
2 touches
0 conflicts
0x211da21b…e9d7
0x34b655…2a6f
2 touches
0 conflicts
0x224d6800…4508
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
1 conflict on slot
0x4cabb80a0e…7546bf
Audit this contract →
← previous block
·
next block →
recent activity