pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#87,051,854
← previous block
next block →
recent activity
Analyzing
Block #87,051,854
11 transactions · 10 stateful · 2026-07-11 12:14:04 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,051,854
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
· blocks 1
#5
updatePriceFeedsIfNecessary
#6
allocate
#7
0x0f6795d9
#8
0x6a523404
#9
transfer
#10
setData
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3ba014e3…35d5
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xfc4d32c0…39f9
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x0203ea15…79a7
0x34b655…2a6f
2 touches
0 conflicts
0x18dc3f96…0d05
0x34b655…2a6f
2 touches
0 conflicts
0x1d0a04dd…b892
0x34b655…2a6f
2 touches
0 conflicts
0x2ee8f4a2…7e1c
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
0x3ba014e38a…cf35d5
Audit this contract →
← previous block
·
next block →
recent activity