pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#87,305,223
← previous block
next block →
recent activity
Analyzing
Block #87,305,223
10 transactions · 8 stateful · 2026-07-12 16:28:19 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,305,223
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
withdraw
#2
0x0f6795d9
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
0x39abec6b
#7
0x0f6795d9
· blocks 1
#9
setData
#8
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x94b8e9d6…77d6
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x04274682…ae3a
0x2ab50b…5c41
2 touches
0 conflicts
0x07976812…084a
0x2ab50b…5c41
2 touches
0 conflicts
0x0849cefc…6a65
0x2ab50b…5c41
2 touches
0 conflicts
0x0b7c503f…0e4c
0x2ab50b…5c41
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
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
0x94b8e9d64e…da77d6
Audit this contract →
← previous block
·
next block →
recent activity