pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,290,398
← previous block
next block →
recent activity
Analyzing
Block #94,290,398
10 transactions · 7 stateful · 2026-08-08 19:39:14 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,290,398
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
updateDataFeedsValuesPartial
#3
aggregate3
#4
execFwdPositionOps
· blocks 1
#6
repayWithCollateral
#7
0xed82b078
#8
approve
#9
setData
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb0c14558…6eda
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x039f1f6c…3155
0x34b655…2a6f
2 touches
0 conflicts
0x21ef0807…d889
0x34b655…2a6f
2 touches
0 conflicts
0x24dd2c1a…8f79
0x34b655…2a6f
2 touches
0 conflicts
0x2ad29b13…92e0
0x34b655…2a6f
2 touches
0 conflicts
0x34806b11…bdf5
0x34b655…2a6f
2 touches
0 conflicts
0x34a1ee7e…fb20
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
0xb0c14558fa…de6eda
Audit this contract →
← previous block
·
next block →
recent activity