pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,538,531
← previous block
next block →
recent activity
Analyzing
Block #92,538,531
9 transactions · 8 stateful · 2026-08-02 16:39:21 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,538,531
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
permit2TransferAndMulticall
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x94defb17
#5
execFwdPositionOps
· blocks 1
#8
0x6a6f7331
#6
execFwdPositionOps
· blocks 1
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x745a7fd6…5fea
0x34b655…2a6f
4 touches
1 conflict
0xa0d3a786…91d9
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x1825deaa…f973
0x09475a…400f
2 touches
0 conflicts
0x00000000…0002
0x1c8a33…d316
2 touches
0 conflicts
0x856d36e4…f467
0x5a66a5…cba8
2 touches
0 conflicts
0x00000000…0003
0x98a45d…206a
2 touches
0 conflicts
0x00000000…0004
0x98a45d…206a
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
0x745a7fd6fd…595fea
Audit this contract →
← previous block
·
next block →
recent activity