pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,196,422
← previous block
next block →
recent activity
Analyzing
Block #94,196,422
14 transactions · 14 stateful · 2026-08-08 11:42:59 UTC
Parallelism
86
/100
Blocked
7
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,196,422
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#2
withdraw
#3
updatePrices
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
#6
0x222d4ad6
#7
0x29eed2d3
#8
batchUpdate
#10
0xed82b078
#11
0x6a7716ba
#12
transfer
#13
setData
#9
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x12d867cc…b97c
0x34b655…2a6f
4 touches
1 conflict
0xc1f6acda…6abb
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x405cd70a…e6ae
0x1c8a33…d316
2 touches
0 conflicts
0xab94749e…6100
0x1c8a33…d316
2 touches
0 conflicts
0xf77a4626…ac01
0x1c8a33…d316
2 touches
0 conflicts
0x1d0a04dd…b892
0x34b655…2a6f
2 touches
0 conflicts
0x1d9867ad…6d9a
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
0x12d867cc46…19b97c
Audit this contract →
← previous block
·
next block →
recent activity