pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,133,932
← previous block
next block →
recent activity
Analyzing
Block #94,133,932
10 transactions · 10 stateful · 2026-08-08 06:26:16 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,133,932
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 1
#6
0x3f5c179b
#7
0x6a76cc80
#8
0x25bd1cf0
#9
setData
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c11fd01…6239
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb6b61477…ed3e
0x34b655…2a6f
4 touches
1 conflict
0x0bfb4aa3…2132
0x34b655…2a6f
2 touches
0 conflicts
0x1bf8d2af…d140
0x34b655…2a6f
2 touches
0 conflicts
0x262d5015…771b
0x34b655…2a6f
2 touches
0 conflicts
0x28e5dbea…2f7f
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
0x1c11fd0187…226239
Audit this contract →
← previous block
·
next block →
recent activity