pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,176,937
← previous block
next block →
recent activity
Analyzing
Block #93,176,937
11 transactions · 10 stateful · 2026-08-04 22:13:21 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,176,937
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#3
updatePriceFeedsIfNecessary
#4
execFwdPositionOps
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
0x6a726478
#8
setData
#9
0x59558d29
#10
0xc7e3ec2c
#2
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8495ea8…10e6
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x6fb92ed4…7205
0x34b655…2a6f
4 touches
1 conflict
0x046740ca…4065
0x34b655…2a6f
2 touches
0 conflicts
0x046740ca…4066
0x34b655…2a6f
2 touches
0 conflicts
0x09396f14…669f
0x34b655…2a6f
2 touches
0 conflicts
0x141cd942…56ac
0x34b655…2a6f
2 touches
0 conflicts
0x232f95c2…1d16
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
0xe8495ea873…3410e6
Audit this contract →
← previous block
·
next block →
recent activity