pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,852,372
← previous block
next block →
recent activity
Analyzing
Block #94,852,372
8 transactions · 7 stateful · 2026-08-10 18:56:29 UTC
Parallelism
50
/100
Blocked
43
%
Avg conflicts / tx
0.63
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,852,372
· 8 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
execOrder
· blocks 3
#2
updateDataFeedsValuesPartial
#6
forward
#7
setData
#3
execOrders
· blocks 1
#4
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
4
w2
5
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07d8b1e8…78c6
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x4ec9ff52…e6f7
0x34b655…2a6f
4 touches
1 conflict
0xee8237bd…46ad
0x34b655…2a6f
4 touches
1 conflict
0x1e10796e…6213
0x34b655…2a6f
2 touches
0 conflicts
0x3055b4d0…81c0
0x34b655…2a6f
2 touches
0 conflicts
0x46c8e565…d7a8
0x34b655…2a6f
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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
0x07d8b1e8f0…0978c6
Audit this contract →
← previous block
·
next block →
recent activity