pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,771,870
← previous block
next block →
recent activity
Analyzing
Block #86,771,870
12 transactions · 9 stateful · 2026-07-10 05:02:57 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,771,870
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execute
#3
0x98717539
· blocks 1
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
#6
0x3f5c179b
#8
forward
#9
execFwdPositionOps
#10
setData
#11
0xb8915e…8ba7
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f6ecd4e…0af0
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x1bfc029c…f91e
0x34b655…2a6f
4 touches
1 conflict
0x9f287382…28e5
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0xc7de062c…6eb6
0x34b655…2a6f
3 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
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
0x5f6ecd4e04…100af0
Audit this contract →
← previous block
·
next block →
recent activity