pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,938,340
← previous block
next block →
recent activity
Analyzing
Block #101,938,340
11 transactions · 10 stateful · 2026-09-04 15:39:15 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
#101,938,340
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
execOrder
· blocks 1
#3
0x59558d29
#4
execPerpOps
#5
execPerpOps
#6
setData
#8
execFwdPositionOpsV2
#9
cancelBatch
#10
batchUpdatePrice
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe35c7ec0…fc77
0x34b655…2a6f
4 touches
1 conflict
0x24ed74ea…a3ff
0x34b655…2a6f
4 touches
1 conflict
0x46356904…5ead
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x0490581d…adaf
0x34b655…2a6f
2 touches
0 conflicts
0x0ad3355f…be85
0x34b655…2a6f
2 touches
0 conflicts
0x142029ac…e80f
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
0xe35c7ec04e…f1fc77
Audit this contract →
← previous block
·
next block →
recent activity