pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,068,190
← previous block
next block →
recent activity
Analyzing
Block #90,068,190
10 transactions · 7 stateful · 2026-07-25 01:10:26 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,068,190
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
execFwdPositionOps
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x3f5c179b
#6
execFwdPositionOps
#7
0x6a640d7a
#8
setData
#9
0xc7e3ec2c
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9834665…e363
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x007155f2…b938
0x34b655…2a6f
2 touches
0 conflicts
0x152f8e3d…3da0
0x34b655…2a6f
2 touches
0 conflicts
0x216ffe66…1f94
0x34b655…2a6f
2 touches
0 conflicts
0x21be5a4c…a301
0x34b655…2a6f
2 touches
0 conflicts
0x31b61a13…ca9f
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
0xb983466539…cee363
Audit this contract →
← previous block
·
next block →
recent activity