pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,752,199
← previous block
next block →
recent activity
Analyzing
Block #94,752,199
9 transactions · 8 stateful · 2026-08-10 10:32:20 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,752,199
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
#2
execOrder
· blocks 1
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
handleOps
#7
execFwdPositionOps
#8
setData
#3
execOrder
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf4f9cac7…fd98
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2328941c…84d3
0x34b655…2a6f
2 touches
0 conflicts
0x441923dd…d1a6
0x34b655…2a6f
2 touches
0 conflicts
0x46404287…8838
0x34b655…2a6f
2 touches
0 conflicts
0x5502e1cc…3910
0x34b655…2a6f
2 touches
0 conflicts
0x66dcc428…6df1
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
0xf4f9cac7d9…09fd98
Audit this contract →
← previous block
·
next block →
recent activity