pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,950,730
← previous block
next block →
recent activity
Analyzing
Block #94,950,730
10 transactions · 9 stateful · 2026-08-11 03:11:10 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,950,730
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 1
#2
placeAndExecuteMarketBuy
#3
execFwdPositionOps
· blocks 1
#5
updateDataFeedsValuesPartial
#6
0x6a7a9346
#7
setData
#8
0x59558d29
#4
execFwdPositionOps
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
4
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x071ff290…ec09
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x1a5d321d…a474
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x747f609d…1555
0x34b655…2a6f
2 touches
0 conflicts
0x7ec9cda3…6ddb
0x34b655…2a6f
2 touches
0 conflicts
0x84d74093…7808
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
0x071ff2901a…8fec09
Audit this contract →
← previous block
·
next block →
recent activity