pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,712,192
← previous block
next block →
recent activity
Analyzing
Block #89,712,192
10 transactions · 9 stateful · 2026-07-23 19:15:42 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
#89,712,192
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
0x5a5d9a99
#3
0x5a5d9a99
· blocks 1
#5
execFwdPositionOps
#6
updateDataFeedsValuesPartial
#7
0x3f5c179b
#8
0x6a6268d6
#9
setData
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbe4a325a…ac1e
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x03695af7…8944
0x34b655…2a6f
2 touches
0 conflicts
0x2003d8cf…6836
0x34b655…2a6f
2 touches
0 conflicts
0x36890fff…f3d1
0x34b655…2a6f
2 touches
0 conflicts
0x4ab0fef9…caef
0x34b655…2a6f
2 touches
0 conflicts
0x4b0906c2…1abe
0x34b655…2a6f
2 touches
0 conflicts
0x51028c5e…235c
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
0xbe4a325aa4…cfac1e
Audit this contract →
← previous block
·
next block →
recent activity