pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,470,951
← previous block
next block →
recent activity
Analyzing
Block #92,470,951
12 transactions · 10 stateful · 2026-08-02 10:59:25 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,470,951
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#4
0x3f5c179b
#5
0x57368ddf
#6
execFwdPositionOps
#8
execOrders
#9
0x6a6f2385
#10
transfer
#11
setData
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf788c790…e66f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0463db49…5d05
0x34b655…2a6f
2 touches
0 conflicts
0x064a19b6…3f1d
0x34b655…2a6f
2 touches
0 conflicts
0x2dea053f…c760
0x34b655…2a6f
2 touches
0 conflicts
0x342222e8…2ec4
0x34b655…2a6f
2 touches
0 conflicts
0x349f436e…80e6
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
0xf788c79025…f8e66f
Audit this contract →
← previous block
·
next block →
recent activity