pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,839,378
← previous block
next block →
recent activity
Analyzing
Block #89,839,378
8 transactions · 7 stateful · 2026-07-24 05:57:51 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,839,378
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x785f5745
#3
execFwdPositionOps
· blocks 1
#4
execFwdPositionOps
· blocks 1
#6
0x6a62ff57
#7
setData
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a6a8d34…dc00
0x34b655…2a6f
4 touches
1 conflict
0x92145e19…6904
0x34b655…2a6f
4 touches
1 conflict
0xf0481793…1ec5
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x5ea9eca9…22a7
0x34b655…2a6f
4 touches
1 conflict
0x5ea9eca9…22a6
0x34b655…2a6f
4 touches
1 conflict
0x518b09b0…76da
0x34b655…2a6f
3 touches
1 conflict
0x1f6b3349…3e21
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
0x1a6a8d34d3…19dc00
Audit this contract →
← previous block
·
next block →
recent activity