pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,739,059
← previous block
next block →
recent activity
Analyzing
Block #94,739,059
12 transactions · 10 stateful · 2026-08-10 09:25:23 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,739,059
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
· blocks 1
#2
execOrders
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 1
#6
forward
#7
placeAndExecuteMarketBuy
#8
0x6a79997b
#9
transfer
#10
setData
#11
0xc7e3ec2c
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x0127457b…f634
0x34b655…2a6f
4 touches
1 conflict
0x92fa1dc0…b239
0x34b655…2a6f
4 touches
1 conflict
0xf18e87f5…6880
0x34b655…2a6f
4 touches
1 conflict
0x786d66ce…ae70
0x34b655…2a6f
3 touches
1 conflict
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
0x482471adbb…39122f
Audit this contract →
← previous block
·
next block →
recent activity