pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,766,920
← previous block
next block →
recent activity
Analyzing
Block #92,766,920
10 transactions · 10 stateful · 2026-08-03 11:49:15 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,766,920
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#4
batchUpdate
#6
commit
#7
setData
#8
0x59558d29
#9
0xc7e3ec2c
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9365e097…ff56
0x34b655…2a6f
4 touches
1 conflict
0x94aff148…b584
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00e21a9f…3583
0x34b655…2a6f
2 touches
0 conflicts
0x0d2de0f6…e6c6
0x34b655…2a6f
2 touches
0 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
2 touches
0 conflicts
0x16e06a6b…4395
0x34b655…2a6f
2 touches
0 conflicts
0x18978822…2623
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
0x9365e0978e…fbff56
Audit this contract →
← previous block
·
next block →
recent activity