pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,862,202
← previous block
next block →
recent activity
Analyzing
Block #94,862,202
10 transactions · 9 stateful · 2026-08-10 19:45:55 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,862,202
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
execOrders
· blocks 2
#3
updateDataFeedsValuesPartial
#6
forward
#7
execFwdPositionOps
#8
setData
#9
0x59558d29
#4
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac3e4969…39e9
0x34b655…2a6f
6 touches
3 conflicts
0xcda18b0b…6a4c
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x16ef6aaa…6eb2
0x34b655…2a6f
2 touches
0 conflicts
0x216ffe66…1f94
0x34b655…2a6f
2 touches
0 conflicts
0x28ceceef…ecc2
0x34b655…2a6f
2 touches
0 conflicts
0x297e2bcf…a3eb
0x34b655…2a6f
2 touches
0 conflicts
0x3111a64f…eb7f
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
3 conflicts on slot
0xac3e4969cf…1739e9
Audit this contract →
← previous block
·
next block →
recent activity