pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,772,350
← previous block
next block →
recent activity
Analyzing
Block #89,772,350
10 transactions · 9 stateful · 2026-07-24 00:19:33 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,772,350
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
0x5a5d9a99
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 2
#6
0x3f5c179b
#7
0x3f5c179b
#8
setData
#5
execFwdPositionOps
· blocks 1
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x80656e3b…9240
0x34b655…2a6f
6 touches
3 conflicts
0xe2e52e46…0894
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x74f95963…01a2
0x34b655…2a6f
4 touches
1 conflict
0x14b29ddb…0fd3
0x34b655…2a6f
2 touches
0 conflicts
0x25e6f91a…a6a4
0x34b655…2a6f
2 touches
0 conflicts
0x5c79a7db…b7aa
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
3 conflicts on slot
0x80656e3b9f…e39240
Audit this contract →
← previous block
·
next block →
recent activity