pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,222,758
← previous block
next block →
recent activity
Analyzing
Block #92,222,758
9 transactions · 8 stateful · 2026-08-01 14:11:14 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,222,758
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
execFwdPositionOps
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#6
execOrders
#7
setData
#8
0x59558d29
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x742c8909…ac72
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x64ac7e40…5d7d
0x34b655…2a6f
4 touches
1 conflict
0x1c582483…7b74
0x34b655…2a6f
4 touches
1 conflict
0x15b254ac…664f
0x34b655…2a6f
2 touches
0 conflicts
0x1827473d…3bcc
0x34b655…2a6f
2 touches
0 conflicts
0x1dfc34bb…34e9
0x34b655…2a6f
2 touches
0 conflicts
0x1dfc34bb…34ea
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
0x742c890919…7fac72
Audit this contract →
← previous block
·
next block →
recent activity