pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,851,280
← previous block
next block →
recent activity
Analyzing
Block #94,851,280
10 transactions · 9 stateful · 2026-08-10 18:50:59 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,851,280
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xeb282f7f
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#5
setData
#6
0x3f5c179b
#7
updatePosition
#9
execFwdPositionOps
#4
execFwdPositionOps
· blocks 1
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac3bc39a…72e0
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…006f
0x1efe02…37d6
2 touches
0 conflicts
0x9f5ccabd…bfb5
0x1efe02…37d6
2 touches
0 conflicts
0xa916a5af…1459
0x1efe02…37d6
2 touches
0 conflicts
0xfa1b3dd2…4d32
0x1efe02…37d6
2 touches
0 conflicts
0x00000000…0099
0xaa3145…feec
2 touches
0 conflicts
0x6a880a13…9082
0xaa3145…feec
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
0xac3bc39ab5…8572e0
Audit this contract →
← previous block
·
next block →
recent activity