pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,577,010
← previous block
next block →
recent activity
Analyzing
Block #89,577,010
10 transactions · 8 stateful · 2026-07-23 05:42:37 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
#89,577,010
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5bf9264c
#2
0x5bf9264c
#3
updatePrices
#4
updateDataFeedsValuesPartial
#5
0x0f6795d9
· blocks 1
#7
0x0f6795d9
#8
0x6a61aa44
#9
setData
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9e70dadd…810d
0x34b655…2a6f
4 touches
1 conflict
0x9e70dadd…810e
0x34b655…2a6f
4 touches
1 conflict
0xab599cc8…29dd
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x4e1de22c…2615
0x34b655…2a6f
4 touches
1 conflict
0x1941b441…5889
0x34b655…2a6f
2 touches
0 conflicts
0x3269d9db…f766
0x34b655…2a6f
2 touches
0 conflicts
0x342f88f5…2a06
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
0x9e70dadd35…1b810d
Audit this contract →
← previous block
·
next block →
recent activity