pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,833,597
← previous block
next block →
recent activity
Analyzing
Block #91,833,597
12 transactions · 8 stateful · 2026-07-31 05:33:48 UTC
Parallelism
83
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,833,597
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execPerpOps
#2
execPerpOps
#3
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
#6
updateDataFeedsValuesPartial
#7
0x3f5c179b
#8
execFwdPositionOps
#9
execOrders
#10
execOrders
#11
setData
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfb4d2081…25ac
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e65
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x6985d93b…1414
0x34b655…2a6f
4 touches
1 conflict
0xb9834665…e363
0x34b655…2a6f
2 touches
0 conflicts
0xcfbf8be4…1a0b
0x34b655…2a6f
2 touches
0 conflicts
0x4e621c19…6089
0x34b655…2a6f
2 touches
0 conflicts
0x57bcf61d…bcbf
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
0xfb4d208173…1f25ac
Audit this contract →
← previous block
·
next block →
recent activity