pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#88,186,925
← previous block
next block →
recent activity
Analyzing
Block #88,186,925
8 transactions · 7 stateful · 2026-07-16 18:47:06 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#88,186,925
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#4
verifyOracleProofV2
#6
0x765aeb4f
#7
setData
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb415dca6…5bdd
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xa27f1875…0c5d
0x34b655…2a6f
4 touches
1 conflict
0xa37f6251…f3c1
0x34b655…2a6f
4 touches
1 conflict
0xad15ca0d…a3d5
0x34b655…2a6f
4 touches
1 conflict
0xb415dca6…5bdc
0x34b655…2a6f
4 touches
1 conflict
0x63cd0a9b…19e8
0x34b655…2a6f
3 touches
1 conflict
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
0xb415dca689…e35bdd
Audit this contract →
← previous block
·
next block →
recent activity