pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,441,508
← previous block
next block →
recent activity
Analyzing
Block #90,441,508
12 transactions · 11 stateful · 2026-07-26 08:47:03 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,441,508
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
transfer
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
· blocks 1
#6
executeBatch
#9
0x6a65c9ff
#10
0xe9316489
#11
setData
#7
execFwdPositionOps
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w0
7
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcbe863a2…b2dd
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x8b66399b…8d29
0x34b655…2a6f
4 touches
1 conflict
0x9e70dadd…810d
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
0xcbe863a2b2…7fb2dd
Audit this contract →
← previous block
·
next block →
recent activity