pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,973,380
← previous block
next block →
recent activity
Analyzing
Block #92,973,380
10 transactions · 8 stateful · 2026-08-04 05:08:06 UTC
Parallelism
70
/100
Blocked
38
%
Avg conflicts / tx
0.4
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,973,380
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
· blocks 1
#2
0x5acec890
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 2
#5
forward
#9
setData
#6
execFwdPositionOps
· blocks 1
#8
0xed82b078
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w0
6
w1
7
w2
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x58123a85…6f7d
0x34b655…2a6f
6 touches
3 conflicts
0xebac0f82…a49c
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x1b77e6f7…53d7
0x34b655…2a6f
4 touches
1 conflict
0x23769ebc…c8ed
0x34b655…2a6f
4 touches
1 conflict
0x4e51608d…c994
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
0x92385428ad…dc6941
Audit this contract →
← previous block
·
next block →
recent activity