pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,231,043
← previous block
next block →
recent activity
Analyzing
Block #94,231,043
10 transactions · 7 stateful · 2026-08-08 14:38:22 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,231,043
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5acec890
· blocks 1
#3
execOrders
#4
execOrders
#5
updateDataFeedsValuesPartial
#6
execFwdPositionOps
#8
0x6a773fd6
#9
setData
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbb322930…ace5
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x206f4379…e08a
0x34b655…2a6f
2 touches
0 conflicts
0x224ff7ce…f233
0x34b655…2a6f
2 touches
0 conflicts
0x38855b14…b4ec
0x34b655…2a6f
2 touches
0 conflicts
0x3cf50d44…961b
0x34b655…2a6f
2 touches
0 conflicts
0x4e58f1d6…2fca
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
0xbb32293008…46ace5
Audit this contract →
← previous block
·
next block →
recent activity