pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,235,445
← previous block
next block →
recent activity
Analyzing
Block #94,235,445
10 transactions · 8 stateful · 2026-08-08 15:00:45 UTC
Parallelism
70
/100
Blocked
25
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,235,445
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5acec890
· blocks 2
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0x3f5c179b
#7
forward
#8
execFwdPositionOps
#9
setData
#2
0x5acec890
· blocks 1
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xabb0951a…273a
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x18ec97d9…6baa
0x34b655…2a6f
2 touches
0 conflicts
0x1e81a9a0…46aa
0x34b655…2a6f
2 touches
0 conflicts
0x27a78688…b891
0x34b655…2a6f
2 touches
0 conflicts
0x3499d04b…5b2b
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
0xabb0951ad6…c8273a
Audit this contract →
← previous block
·
next block →
recent activity