pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,455,043
← previous block
next block →
recent activity
Analyzing
Block #87,455,043
9 transactions · 8 stateful · 2026-07-13 09:10:14 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,455,043
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
0x5a5d9a99
#3
updateDataFeedsValuesPartial
#4
executeBatch
#5
execFwdPositionOps
· blocks 1
#7
execFwdPositionOps
#8
setData
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9b02ba92…7100
0x34b655…2a6f
4 touches
1 conflict
0xc2f84a16…86b8
0x34b655…2a6f
4 touches
1 conflict
0xb568bd0a…0a73
0x34b655…2a6f
4 touches
1 conflict
0x0387281b…6aab
0x34b655…2a6f
4 touches
1 conflict
0xb568bd0a…0a72
0x34b655…2a6f
4 touches
1 conflict
0x0d3db6d5…2e39
0x34b655…2a6f
4 touches
1 conflict
0x346e6e22…8deb
0x34b655…2a6f
4 touches
1 conflict
0x3f93d576…f1de
0x34b655…2a6f
4 touches
1 conflict
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
0x9b02ba92fc…e87100
Audit this contract →
← previous block
·
next block →
recent activity