pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,164,736
← previous block
next block →
recent activity
Analyzing
Block #91,164,736
10 transactions · 9 stateful · 2026-07-28 21:26:41 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
#91,164,736
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#3
batchUpdate
#4
execFwdPositionOps
#5
forward
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
0x6a691f09
#9
setData
#2
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf4f9cac7…fd98
0x34b655…2a6f
4 touches
1 conflict
0x5502e1cc…3910
0x34b655…2a6f
4 touches
1 conflict
0x81561f70…fefd
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x18de6e82…7ec0
0x34b655…2a6f
2 touches
0 conflicts
0x1f32a18c…e9bb
0x34b655…2a6f
2 touches
0 conflicts
0x3acc628e…e425
0x34b655…2a6f
2 touches
0 conflicts
0x41469894…598f
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
0xf4f9cac7d9…09fd98
Audit this contract →
← previous block
·
next block →
recent activity