pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,543,817
← previous block
next block →
recent activity
Analyzing
Block #89,543,817
8 transactions · 8 stateful · 2026-07-23 02:00:52 UTC
Parallelism
75
/100
Blocked
25
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,543,817
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
0x5a5d9a99
#3
execFwdPositionOps
· blocks 2
#4
updateDataFeedsValuesPartial
#7
setData
#5
execFwdPositionOps
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfec3435f…4a72
0x34b655…2a6f
4 touches
1 conflict
0xb30f0bf0…ff6f
0x34b655…2a6f
4 touches
1 conflict
0xb900efa2…8624
0x34b655…2a6f
4 touches
1 conflict
0xdb89ef9a…606c
0x34b655…2a6f
4 touches
1 conflict
0xe403bf26…7943
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2ee5c07b…7eb9
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
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
1 conflict on slot
0xfec3435f10…8e4a72
Audit this contract →
← previous block
·
next block →
recent activity