pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,057,555
← previous block
next block →
recent activity
Analyzing
Block #87,057,555
9 transactions · 8 stateful · 2026-07-11 12:52:14 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,057,555
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
0x5a5d9a99
#3
execFwdPositionOps
· blocks 1
#4
execFwdPositionOps
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#8
setData
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3be33cca…1000
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xa0237ed3…2622
0x34b655…2a6f
4 touches
1 conflict
0x8dca3e45…a5b3
0x34b655…2a6f
4 touches
1 conflict
0xd8f13f52…d1a8
0x34b655…2a6f
4 touches
1 conflict
0x3be33cca…0fff
0x34b655…2a6f
4 touches
1 conflict
0xafb85eec…2ee4
0x34b655…2a6f
3 touches
1 conflict
0xd8fd2add…50fc
0x69df8a…6292
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
0x3be33cca63…661000
Audit this contract →
← previous block
·
next block →
recent activity