pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,078,165
← previous block
next block →
recent activity
Analyzing
Block #87,078,165
10 transactions · 10 stateful · 2026-07-11 15:09:39 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
#87,078,165
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
0x785f5745
#3
execFwdPositionOps
#4
execFwdPositionOps
· blocks 1
#5
updateDataFeedsValuesPartial
#7
execOrders
#8
0x6a525d2a
#9
setData
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbb30c41f…1385
0x34b655…2a6f
4 touches
1 conflict
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0xc449c25f…4f90
0x34b655…2a6f
4 touches
1 conflict
0x58627b98…92ae
0x34b655…2a6f
4 touches
1 conflict
0x58627b98…92ad
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xa248a5dd…4a69
0x34b655…2a6f
4 touches
1 conflict
0x0a7e57b0…d0c5
0x34b655…2a6f
3 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
0xbb30c41f6d…a21385
Audit this contract →
← previous block
·
next block →
recent activity