pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,422,335
← previous block
next block →
recent activity
Analyzing
Block #91,422,335
14 transactions · 11 stateful · 2026-07-29 19:04:00 UTC
Parallelism
86
/100
Blocked
27
%
Avg conflicts / tx
0.21
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,422,335
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
0x6ad2e98b
· blocks 2
#3
0x6ad2e98b
#5
updatePrices
· blocks 1
#7
updatePrices
#8
updateDataFeedsValuesPartial
#9
executeBatch
#11
execFwdPositionOps
#12
setData
#13
0x59558d29
#4
0xab083028
#6
updatePrices
#10
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
5
w0
6
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb8644937…ed09
0x851145…3f07
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0002
0x48cba2…b48b
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x736974b6…87a6
0x000000…012a
2 touches
0 conflicts
0x56a919c4…ab49
0x01bff4…1071
2 touches
0 conflicts
0x7730bc45…be06
0x01bff4…1071
2 touches
0 conflicts
0xb1a4d6b6…304f
0x01bff4…1071
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:
0x851145ea…9f3f07
1 conflict on slot
0xb864493701…12ed09
Audit this contract →
← previous block
·
next block →
recent activity