pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#104,194,493
← previous block
next block →
recent activity
Analyzing
Block #104,194,493
9 transactions · 8 stateful · 2026-09-12 13:43:28 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#104,194,493
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x59558d29
#3
executeBatch
#4
setData
#5
execFwdPositionOpsV2
· blocks 2
#8
execOrders
#6
execFwdPositionOpsV2
· blocks 1
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea559e7b…41f4
0x34b655…2a6f
6 touches
3 conflicts
0xa46242d8…c0a7
0x34b655…2a6f
6 touches
3 conflicts
0xc8a5a1be…dcfd
0x34b655…2a6f
5 touches
3 conflicts
0x0da71bf6…4d35
0x34b655…2a6f
4 touches
1 conflict
0x5e7e0120…7bb9
0x34b655…2a6f
4 touches
1 conflict
0xb0b39b82…c11e
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
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
0xea559e7b33…d641f4
Audit this contract →
← previous block
·
next block →
recent activity