pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#88,350,191
← previous block
next block →
recent activity
Analyzing
Block #88,350,191
11 transactions · 9 stateful · 2026-07-17 12:58:47 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#88,350,191
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x0f6795d9
· blocks 1
#4
0xc5a04723
#5
forward
#6
0x0f6795d9
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
updateDataFeedsValuesPartial
#10
setData
#3
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea1b8c07…b969
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x046740ca…4065
0x34b655…2a6f
2 touches
0 conflicts
0x046740ca…4066
0x34b655…2a6f
2 touches
0 conflicts
0x05896939…9f49
0x34b655…2a6f
2 touches
0 conflicts
0x072363c3…d830
0x34b655…2a6f
2 touches
0 conflicts
0x0eaa3f4e…2992
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
0xea1b8c07ee…d0b969
Audit this contract →
← previous block
·
next block →
recent activity