pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,850,674
← previous block
next block →
recent activity
Analyzing
Block #90,850,674
11 transactions · 10 stateful · 2026-07-27 19:05:47 UTC
Parallelism
73
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,850,674
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5a5d9a99
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 1
#6
executeBatch
#8
commit
#9
0x6a67ac80
#10
setData
#5
execFwdPositionOps
· blocks 1
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x836544ae…79e6
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcc
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcd
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x0110331c…b891
0x34b655…2a6f
2 touches
0 conflicts
0x344bc09a…942f
0x34b655…2a6f
2 touches
0 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
2 touches
0 conflicts
0xa80684c9…3948
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
0x836544ae2a…5879e6
Audit this contract →
← previous block
·
next block →
recent activity