pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,351,511
← previous block
next block →
recent activity
Analyzing
Block #86,351,511
10 transactions · 10 stateful · 2026-07-08 06:11:23 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,351,511
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x0f6795d9
#3
0x0f6795d9
· blocks 1
#4
handleOps
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
0x6a4dea82
#9
setData
#5
0x0f6795d9
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
0xc8304415…4f91
0x34b655…2a6f
4 touches
1 conflict
0x08e2668d…5722
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x052aead1…4ebb
0x34b655…2a6f
2 touches
0 conflicts
0x0d2de0f6…e6c6
0x34b655…2a6f
2 touches
0 conflicts
0x13b176eb…8e71
0x34b655…2a6f
2 touches
0 conflicts
0x1779ca58…5040
0x34b655…2a6f
2 touches
0 conflicts
0x1bee5aea…5f61
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
0xc8304415c6…574f91
Audit this contract →
← previous block
·
next block →
recent activity