pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,056,940
← previous block
next block →
recent activity
Analyzing
Block #87,056,940
8 transactions · 7 stateful · 2026-07-11 12:48:07 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
#87,056,940
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
updateDataFeedsValuesPartial
#3
0x3f5c179b
#4
execFwdPositionOps
#5
execFwdPositionOps
· blocks 1
#7
setData
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2307994…acad
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xa4e3b3b1…0911
0x2a68ba…90c5
2 touches
0 conflicts
0x5bb46f6c…7693
0x34b655…2a6f
2 touches
0 conflicts
0xcdd95ca7…a9c8
0x34b655…2a6f
2 touches
0 conflicts
0xf5042875…9a93
0x34b655…2a6f
2 touches
0 conflicts
0xfcdb5918…2b49
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
0xe2307994ef…00acad
Audit this contract →
← previous block
·
next block →
recent activity