pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,867,298
← previous block
next block →
recent activity
Analyzing
Block #90,867,298
8 transactions · 6 stateful · 2026-07-27 20:29:28 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,867,298
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
#2
executeBatch
#3
execFwdPositionOps
· blocks 1
#4
execFwdPositionOps
· blocks 1
#6
updateDataFeedsValuesPartial
#7
setData
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x8d7e3f62…e2cc
0x34b655…2a6f
4 touches
1 conflict
0x8d7e3f62…e2cd
0x34b655…2a6f
4 touches
1 conflict
0xb5dab803…6922
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xfb31d278…9107
0x34b655…2a6f
4 touches
1 conflict
0x33be4b45…d981
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
1 conflict on slot
0x482471adbb…39122f
Audit this contract →
← previous block
·
next block →
recent activity