pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,487,962
← previous block
next block →
recent activity
Analyzing
Block #87,487,962
8 transactions · 6 stateful · 2026-07-13 12:50:19 UTC
Parallelism
63
/100
Blocked
33
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,487,962
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
execOrder
#3
execFwdPositionOps
· blocks 2
#4
updateDataFeedsValuesPartial
#7
setData
#5
execFwdPositionOps
· blocks 1
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9266685…8b1d
0x34b655…2a6f
6 touches
3 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x03bf1a82…9119
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x26947d85…33c1
0x34b655…2a6f
4 touches
1 conflict
0x2c145401…09fd
0x34b655…2a6f
4 touches
1 conflict
0x367b69ad…33d8
0x34b655…2a6f
4 touches
1 conflict
0x367b69ad…33d9
0x34b655…2a6f
4 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
3 conflicts on slot
0xb92666855b…228b1d
Audit this contract →
← previous block
·
next block →
recent activity