pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,961,685
← previous block
next block →
recent activity
Analyzing
Block #91,961,685
12 transactions · 10 stateful · 2026-07-31 16:18:13 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,961,685
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
addSellOrder
#2
execFwdPositionOps
· blocks 1
#3
0x39abec6b
#4
0x29eed2d3
#5
execOrders
#7
execFwdPositionOps
#8
updateDataFeedsValuesPartial
#9
setData
#10
execOrders
#11
0x59558d29
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x47eeb844…6a02
0x34b655…2a6f
4 touches
1 conflict
0x59127721…bc10
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e65
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x80afd9d9…57cf
0x065c9d…c394
2 touches
0 conflicts
0x08229f31…3cae
0x34b655…2a6f
2 touches
0 conflicts
0x0e21a259…d2ec
0x34b655…2a6f
2 touches
0 conflicts
0x12f97307…97c3
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
0x47eeb844d4…506a02
Audit this contract →
← previous block
·
next block →
recent activity