pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,177,364
← previous block
next block →
recent activity
Analyzing
Block #92,177,364
10 transactions · 9 stateful · 2026-08-01 10:22:58 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,177,364
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
multicall
#2
updateDataFeedsValuesPartial
#3
executeBatch
#4
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
#7
setData
#8
0x59558d29
#9
0xc7e3ec2c
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xa77975dc…94c7
0x09475a…400f
2 touches
0 conflicts
0xc0240a50…d410
0x111111…db61
2 touches
0 conflicts
0xec3e20e7…e008
0x111111…db61
2 touches
0 conflicts
0x1349aa49…4a25
0xbeeffb…5fdb
2 touches
0 conflicts
0xa808ec60…5528
0xbeeffb…5fdb
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
0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block
·
next block →
recent activity