pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#87,256,886
← previous block
next block →
recent activity
Analyzing
Block #87,256,886
10 transactions · 8 stateful · 2026-07-12 11:05:10 UTC
Parallelism
70
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,256,886
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x0f6795d9
#3
0x0f6795d9
· blocks 1
#4
0x3f5c179b
#5
0x0f6795d9
#7
transfer
#8
setData
#6
0x0f6795d9
· blocks 1
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x793aa64d…b09c
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09d
0x34b655…2a6f
4 touches
1 conflict
0x0a0cecef…4ed0
0x34b655…2a6f
4 touches
1 conflict
0x1eff5a2f…f5d7
0x34b655…2a6f
4 touches
1 conflict
0x239122db…dc81
0x34b655…2a6f
2 touches
0 conflicts
0x39c62b87…3717
0x34b655…2a6f
2 touches
0 conflicts
0x3b689fd2…629c
0x34b655…2a6f
2 touches
0 conflicts
0x5009d41c…d779
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
0x793aa64d0d…fdb09c
Audit this contract →
← previous block
·
next block →
recent activity