pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,468,848
← previous block
next block →
recent activity
Analyzing
Block #94,468,848
10 transactions · 9 stateful · 2026-08-09 10:45:52 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,468,848
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
placeAndExecuteMarketBuy
#3
execFwdPositionOps
· blocks 2
#6
updateDataFeedsValuesPartial
#7
setData
#8
execOrders
#9
0xc7e3ec2c
#4
execFwdPositionOps
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x898d9b8a…d1ef
0x34b655…2a6f
4 touches
1 conflict
0xc1feb214…9967
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1dc556e9…ae70
0x065c9d…c394
2 touches
0 conflicts
0x485a26d9…93f7
0x065c9d…c394
2 touches
0 conflicts
0x5ee633cc…5002
0x065c9d…c394
2 touches
0 conflicts
0x62593b6d…a6f5
0x065c9d…c394
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
0x898d9b8ab1…f9d1ef
Audit this contract →
← previous block
·
next block →
recent activity