pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#88,040,194
← previous block
next block →
recent activity
Analyzing
Block #88,040,194
7 transactions · 6 stateful · 2026-07-16 02:24:48 UTC
Parallelism
71
/100
Blocked
33
%
Avg conflicts / tx
0.29
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#88,040,194
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
· blocks 2
#5
setData
#6
execOrders
#3
execFwdPositionOps
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7561f24a…4522
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x013a6b08…d120
0x34b655…2a6f
2 touches
0 conflicts
0x05ae4d3e…3c79
0x34b655…2a6f
2 touches
0 conflicts
0x28d4261c…56c7
0x34b655…2a6f
2 touches
0 conflicts
0x28d4261c…56c8
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
0x7561f24a32…174522
Audit this contract →
← previous block
·
next block →
recent activity