pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,925,041
← previous block
next block →
recent activity
Analyzing
Block #101,925,041
13 transactions · 13 stateful · 2026-09-04 14:31:41 UTC
Parallelism
77
/100
Blocked
15
%
Avg conflicts / tx
0.23
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,925,041
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x6a9ad6c5
#2
deposit
#3
execOrders
#4
updatePrices
· blocks 2
#7
updateDataFeedsValuesPartial
#8
0x59558d29
#9
setData
#10
execFwdPositionOpsV2
#11
execFwdPositionOpsV2
#12
execOrders
#5
updatePrices
· blocks 1
#6
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0de7749d…5bef
0x34b655…2a6f
2 touches
0 conflicts
0x15413337…2a40
0x34b655…2a6f
2 touches
0 conflicts
0x1e9a3fc4…c4e1
0x34b655…2a6f
2 touches
0 conflicts
0x25df4e20…a0ef
0x34b655…2a6f
2 touches
0 conflicts
0x3acc6134…3411
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:
0xf5b5f7f8…a36d70
3 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity