pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,581,229
← previous block
next block →
recent activity
Analyzing
Block #92,581,229
9 transactions · 7 stateful · 2026-08-02 20:14:05 UTC
Parallelism
78
/100
Blocked
29
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,581,229
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
· blocks 1
#4
0x57368ddf
#5
0x6a6fa585
#6
setData
#7
0x59558d29
· blocks 1
#3
execFwdPositionOps
#8
0x59558d29
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c619b7d…f4fa
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00958d6e…1d0a
0x34b655…2a6f
2 touches
0 conflicts
0x0253b3dd…7dd7
0x34b655…2a6f
2 touches
0 conflicts
0x054afe69…16e8
0x34b655…2a6f
2 touches
0 conflicts
0x07ea9e5c…8227
0x34b655…2a6f
2 touches
0 conflicts
0x07fbcab3…79b8
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
0x4c619b7d61…22f4fa
Audit this contract →
← previous block
·
next block →
recent activity