pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,247,514
← previous block
next block →
recent activity
Analyzing
Block #91,247,514
12 transactions · 11 stateful · 2026-07-29 04:23:07 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,247,514
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
0x5a5d9a99
#3
execFwdPositionOps
· blocks 1
#4
execFwdPositionOps
#5
handleOps
#7
updateDataFeedsValuesPartial
#8
0x6a6980a3
#9
setData
#10
execOrders
#11
0x59558d29
#6
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdedb36e7…3585
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x033cf007…136d
0x34b655…2a6f
2 touches
0 conflicts
0x054afe69…16e8
0x34b655…2a6f
2 touches
0 conflicts
0x0a216284…5e14
0x34b655…2a6f
2 touches
0 conflicts
0x0c119c6d…a42e
0x34b655…2a6f
2 touches
0 conflicts
0x0c21cc22…f749
0x34b655…2a6f
2 touches
0 conflicts
0x162ee430…31c3
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
0xdedb36e742…d23585
Audit this contract →
← previous block
·
next block →
recent activity