pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,490,632
← previous block
next block →
recent activity
Analyzing
Block #94,490,632
11 transactions · 10 stateful · 2026-08-09 12:35:29 UTC
Parallelism
73
/100
Blocked
20
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,490,632
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
· blocks 2
#3
execFwdPositionOps
#4
0x3f5c179b
#6
execFwdPositionOps
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
setData
#10
withdraw
#2
execOrders
· blocks 1
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x81561f70…fefd
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x57759c59…fa50
0x34b655…2a6f
4 touches
1 conflict
0xd81ad082…cf8e
0x34b655…2a6f
3 touches
1 conflict
0xf72eb60b…05a9
0x34b655…2a6f
3 touches
1 conflict
0x3e412550…5c60
0x34b655…2a6f
2 touches
0 conflicts
0x45911da6…5523
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
0x81561f70ba…26fefd
Audit this contract →
← previous block
·
next block →
recent activity