pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,856,843
← previous block
next block →
recent activity
Analyzing
Block #90,856,843
12 transactions · 11 stateful · 2026-07-27 19:36:49 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,856,843
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updatePrices
#3
0x5a5d9a99
#4
cancel
#5
execFwdPositionOps
· blocks 1
#7
collect
#8
updateDataFeedsValuesPartial
#9
0x6a67b3c8
#10
setData
#11
execOrders
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6261c4ce…2a4b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd800e635…b1d7
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x11a90f82…8bb6
0x34b655…2a6f
2 touches
0 conflicts
0x33fa9eab…4b3d
0x34b655…2a6f
2 touches
0 conflicts
0x4dc6cd61…f674
0x34b655…2a6f
2 touches
0 conflicts
0x563bbb55…861a
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
0x6261c4ce17…d62a4b
Audit this contract →
← previous block
·
next block →
recent activity