pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,302,508
← previous block
next block →
recent activity
Analyzing
Block #92,302,508
12 transactions · 11 stateful · 2026-08-01 20:52:20 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
#92,302,508
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#2
execFwdPositionOps
· blocks 1
#3
execFwdPositionOps
#4
updateDataFeedsValuesPartial
#6
0x57368ddf
#8
forward
#9
setData
#10
updatePrices
#11
0x59558d29
#5
execFwdPositionOps
#7
placeAndExecuteMarketSell
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
5
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53bda555…3810
0x34b655…2a6f
4 touches
1 conflict
0x5cc477b5…1cf3
0x34b655…2a6f
4 touches
1 conflict
0xc755c95b…6814
0x34b655…2a6f
4 touches
1 conflict
0xe497d480…1188
0x34b655…2a6f
4 touches
1 conflict
0xd6bd849a…5597
0x2a68ba…90c5
4 touches
1 conflict
0x1d44909b…e905
0xa6afd3…d132
3 touches
1 conflict
0x778870e7…2a8a
0xa6afd3…d132
3 touches
1 conflict
0xe2263bea…6a9e
0x2b46c0…1669
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
0x53bda5555c…603810
Audit this contract →
← previous block
·
next block →
recent activity