pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,689,039
← previous block
next block →
recent activity
Analyzing
Block #92,689,039
13 transactions · 13 stateful · 2026-08-03 05:17:13 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,689,039
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#4
0x3f5c179b
#6
batchUpdate
#7
forward
#8
0x6a7024d0
#9
setData
#10
execOrders
#11
0x59558d29
#12
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
0x0fe1e6e0…f553
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0505bae8…b4fb
0x34b655…2a6f
2 touches
0 conflicts
0x1827473d…3bcc
0x34b655…2a6f
2 touches
0 conflicts
0x2020622a…07ae
0x34b655…2a6f
2 touches
0 conflicts
0x2020622a…07af
0x34b655…2a6f
2 touches
0 conflicts
0x309b3111…7769
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
0x0fe1e6e0ec…9df553
Audit this contract →
← previous block
·
next block →
recent activity