pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,050,873
← previous block
next block →
recent activity
Analyzing
Block #92,050,873
12 transactions · 10 stateful · 2026-07-31 23:46:46 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,050,873
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xe3cc74…410f
#2
execute
#3
execFwdPositionOps
· blocks 1
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
0x3f5c179b
#7
execFwdPositionOps
#9
0x6a6d345e
#10
setData
#11
0x59558d29
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33649c4f…b327
0x34b655…2a6f
4 touches
1 conflict
0x4ca1f114…6d26
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xe75ce681…ba5f
0x188d58…ea8e
2 touches
0 conflicts
0xe75ce681…ba61
0x188d58…ea8e
2 touches
0 conflicts
0x14420c60…fe43
0x34b655…2a6f
2 touches
0 conflicts
0x18978822…2623
0x34b655…2a6f
2 touches
0 conflicts
0x1f1b77c3…853e
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
0x33649c4f08…eeb327
Audit this contract →
← previous block
·
next block →
recent activity