pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#74,789,958
← previous block
next block →
recent activity
Analyzing
Block #74,789,958
14 transactions · 11 stateful · 2026-05-15 16:45:27 UTC
Parallelism
86
/100
Blocked
9
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,789,958
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
approve
#2
0x0c7abd22
#3
forward
#4
execPerpOps
#5
execPerpOps
#6
updateDataFeedsValuesPartial
#7
verifyOracleProofV2
#8
createModule
#9
setData
#10
execOrders
· blocks 1
#12
0x42dd8743
#13
jMMeC
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x801a6e57…d85c
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0000
0x16d564…365f
2 touches
0 conflicts
0x00000000…0001
0x16d564…365f
2 touches
0 conflicts
0x00000000…0008
0x16d564…365f
2 touches
0 conflicts
0x00000000…009a
0x16f70c…c3dd
2 touches
0 conflicts
0x72a152dd…a08e
0x16f70c…c3dd
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
0x801a6e5726…c1d85c
Audit this contract →
← previous block
·
next block →
recent activity