pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,543,167
← previous block
next block →
recent activity
Analyzing
Block #90,543,167
10 transactions · 9 stateful · 2026-07-26 17:18:43 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,543,167
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execPerpOps
#2
execPerpOps
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 1
#6
0x3f5c179b
#7
0xed82b078
#8
transfer
#9
setData
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x464085b1…499b
0x34b655…2a6f
4 touches
1 conflict
0xf51ec09c…b4a9
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x03c38bff…f48f
0x34b655…2a6f
2 touches
0 conflicts
0x06d13840…23a1
0x34b655…2a6f
2 touches
0 conflicts
0x0eac6378…36f4
0x34b655…2a6f
2 touches
0 conflicts
0x17b720f5…ad7a
0x34b655…2a6f
2 touches
0 conflicts
0x18de67b0…bf35
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
0x464085b1c0…27499b
Audit this contract →
← previous block
·
next block →
recent activity