pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#88,077,766
← previous block
next block →
recent activity
Analyzing
Block #88,077,766
10 transactions · 9 stateful · 2026-07-16 06:36:04 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#88,077,766
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39435dac
#2
updateDataFeedsValuesPartial
#3
0x4d8dc985
#4
updateDataFeedsValuesPartial
#5
0x3f5c179b
#6
0x0f6795d9
· blocks 1
#8
setData
#9
0xc7e3ec2c
#7
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x3151b440…d0aa
0x34b655…2a6f
2 touches
0 conflicts
0x47774d48…7bac
0x34b655…2a6f
2 touches
0 conflicts
0x509017a7…5208
0x34b655…2a6f
2 touches
0 conflicts
0x5af10b50…8d5c
0x34b655…2a6f
2 touches
0 conflicts
0x64e5f38d…187c
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
0x92385428ad…dc6941
Audit this contract →
← previous block
·
next block →
recent activity