pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,821,555
← previous block
next block →
recent activity
Analyzing
Block #92,821,555
11 transactions · 9 stateful · 2026-08-03 16:24:07 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,821,555
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
· blocks 1
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
#4
execFwdPositionOps
#5
0x3f5c179b
#7
execOrders
#8
0x6a70c11f
#9
setData
#10
0x59558d29
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07d8b1e8…78c6
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x00f6a8a7…0e6e
0x34b655…2a6f
2 touches
0 conflicts
0x0287e69c…74b4
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x9cf9008a…d826
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
0x07d8b1e8f0…0978c6
Audit this contract →
← previous block
·
next block →
recent activity