pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,695,107
← previous block
next block →
recent activity
Analyzing
Block #94,695,107
11 transactions · 10 stateful · 2026-08-10 05:43:55 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,695,107
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xb2d4797b
#2
execOrders
· blocks 1
#3
updateDataFeedsValuesPartial
#5
executeBatch
#6
0x3f5c179b
#7
execFwdPositionOps
#8
0x6a796593
#9
setData
#10
collectFees
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2e52e46…0894
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x09da438b…434f
0x34b655…2a6f
2 touches
0 conflicts
0x1d6cb721…c88c
0x34b655…2a6f
2 touches
0 conflicts
0x2db666e7…b931
0x34b655…2a6f
2 touches
0 conflicts
0x4c3a31f9…cb50
0x34b655…2a6f
2 touches
0 conflicts
0x6507044e…bcd6
0x34b655…2a6f
2 touches
0 conflicts
0x8218911e…3bed
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
0xe2e52e4663…6f0894
Audit this contract →
← previous block
·
next block →
recent activity