pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,204,609
← previous block
next block →
recent activity
Analyzing
Block #94,204,609
9 transactions · 7 stateful · 2026-08-08 12:24:23 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,204,609
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x3f5c179b
#2
execFwdPositionOps
· blocks 1
#4
0xed82b078
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
0x6a77206f
#8
setData
#3
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb2699a97…9c44
0x34b655…2a6f
4 touches
1 conflict
0xbbb0ed09…f29e
0x34b655…2a6f
4 touches
1 conflict
0xcd26fba5…21c6
0x34b655…2a6f
4 touches
1 conflict
0xe7bd356d…d23a
0x34b655…2a6f
4 touches
1 conflict
0xe7bd356d…d23b
0x34b655…2a6f
4 touches
1 conflict
0x428df9ce…4931
0x34b655…2a6f
4 touches
1 conflict
0xa3ed5a09…c6d3
0x34b655…2a6f
4 touches
1 conflict
0x73e28b10…e4cf
0x447d2e…e9f5
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
0xb2699a97c0…d79c44
Audit this contract →
← previous block
·
next block →
recent activity