pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,760,031
← previous block
next block →
recent activity
Analyzing
Block #89,760,031
11 transactions · 9 stateful · 2026-07-23 23:17:19 UTC
Parallelism
73
/100
Blocked
33
%
Avg conflicts / tx
0.36
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,760,031
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 2
#7
execOrders
#8
transfer
· blocks 1
#10
setData
#5
execFwdPositionOps
· blocks 1
#9
transfer
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w2
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd7908b5f…56b9
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd192f4ed…d7ec
0x34b655…2a6f
4 touches
1 conflict
0xea837bf5…8e5a
0x34b655…2a6f
4 touches
1 conflict
0x48e3acd8…cf41
0x34b655…2a6f
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x2d56e62c…60d6
0x34b655…2a6f
4 touches
1 conflict
0x41d7e149…baec
0x34b655…2a6f
4 touches
1 conflict
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
0xd7908b5fe5…2b56b9
Audit this contract →
← previous block
·
next block →
recent activity