pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,917,338
← previous block
next block →
recent activity
Analyzing
Block #86,917,338
8 transactions · 7 stateful · 2026-07-10 21:15:15 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,917,338
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#4
execFwdPositionOps
#6
0x6a51615b
#7
setData
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x779b5947…cee5
0x34b655…2a6f
4 touches
1 conflict
0xab98deda…aec3
0x34b655…2a6f
4 touches
1 conflict
0xab98deda…aec4
0x34b655…2a6f
4 touches
1 conflict
0x7545436b…012e
0x34b655…2a6f
4 touches
1 conflict
0x9f6a8d51…97b9
0x34b655…2a6f
3 touches
1 conflict
0x1b317ce5…002f
0x34b655…2a6f
2 touches
0 conflicts
0x1e6e9104…f143
0x34b655…2a6f
2 touches
0 conflicts
0x1e9d86f5…53a8
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
0x779b594790…8dcee5
Audit this contract →
← previous block
·
next block →
recent activity