pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,431,787
← previous block
next block →
recent activity
Analyzing
Block #90,431,787
12 transactions · 11 stateful · 2026-07-26 07:57:13 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,431,787
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5a5d9a99
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 1
#6
0x3f5c179b
#7
0x3f5c179b
#8
0x6a65be50
#9
setData
#10
execOrders
#11
execOrders
#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
0x17637b08…707f
0x34b655…2a6f
4 touches
1 conflict
0xf63c2a2b…bc5f
0x34b655…2a6f
4 touches
1 conflict
0xf63c2a2b…bc60
0x34b655…2a6f
4 touches
1 conflict
0x589dd47c…eea2
0x34b655…2a6f
4 touches
1 conflict
0x513b0c80…d2d9
0x34b655…2a6f
4 touches
1 conflict
0x175307f4…6edd
0x34b655…2a6f
2 touches
0 conflicts
0x1f94aad9…7ce0
0x34b655…2a6f
2 touches
0 conflicts
0x2a5cca98…7520
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
0x17637b0898…37707f
Audit this contract →
← previous block
·
next block →
recent activity