pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,609,980
← previous block
next block →
recent activity
Analyzing
Block #90,609,980
8 transactions · 8 stateful · 2026-07-26 22:54:50 UTC
Parallelism
50
/100
Blocked
38
%
Avg conflicts / tx
0.5
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,609,980
· 8 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
· blocks 2
#6
setData
#7
0xc7e3ec2c
#3
execFwdPositionOps
· blocks 1
#4
execFwdPositionOps
· blocks 1
#5
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
5
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x30d58b0b…8806
0x34b655…2a6f
4 touches
1 conflict
0x3c0d2f30…1afb
0x34b655…2a6f
4 touches
1 conflict
0xa7c7dd7e…ce22
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7085
0x34b655…2a6f
4 touches
1 conflict
0xd2e49325…0e52
0x34b655…2a6f
3 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
3 conflicts on slot
0x92385428ad…dc6941
Audit this contract →
← previous block
·
next block →
recent activity