pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#88,343,624
← previous block
next block →
recent activity
Analyzing
Block #88,343,624
9 transactions · 7 stateful · 2026-07-17 12:14:49 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#88,343,624
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
#6
execFwdPositionOps
#7
0x6a5a1d31
#8
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
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0xb7a47e62…7963
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0505bae8…b4fb
0x34b655…2a6f
2 touches
0 conflicts
0x0bc47ca8…2456
0x34b655…2a6f
2 touches
0 conflicts
0x0bc47ca8…2457
0x34b655…2a6f
2 touches
0 conflicts
0x18e86f02…fa98
0x34b655…2a6f
2 touches
0 conflicts
0x196c2058…bb2e
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
0x0733be30d6…38112f
Audit this contract →
← previous block
·
next block →
recent activity