pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,419,486
← previous block
next block →
recent activity
Analyzing
Block #92,419,486
8 transactions · 7 stateful · 2026-08-02 06:40:36 UTC
Parallelism
63
/100
Blocked
29
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,419,486
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x5acec890
#3
execFwdPositionOps
· blocks 2
#6
0x6a6ee6dc
#7
setData
#4
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd5f0304e…ed46
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x00958d6e…1d0a
0x34b655…2a6f
4 touches
1 conflict
0xef67b8c0…deec
0x34b655…2a6f
4 touches
1 conflict
0x00958d6e…1d09
0x34b655…2a6f
4 touches
1 conflict
0x34b6e036…2161
0x34b655…2a6f
4 touches
1 conflict
0x38c6ff01…689f
0x34b655…2a6f
4 touches
1 conflict
0x3a5cd535…3546
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot
0xd5f0304ef0…2eed46
Audit this contract →
← previous block
·
next block →
recent activity