pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,687,566
← previous block
next block →
recent activity
Analyzing
Block #89,687,566
9 transactions · 7 stateful · 2026-07-23 17:11:35 UTC
Parallelism
67
/100
Blocked
29
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,687,566
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
0x5a5d9a99
· blocks 1
#5
execFwdPositionOps
#6
0xce1e7030
#7
updateDataFeedsValuesPartial
#8
setData
#3
0x5a5d9a99
· blocks 1
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcbcc67c0…34de
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x7d02a2c5…9802
0x34b655…2a6f
4 touches
1 conflict
0x48ed1159…abe9
0x2b46c0…1669
2 touches
0 conflicts
0xa605468c…1bfc
0x2b46c0…1669
2 touches
0 conflicts
0x18e37e7d…bab2
0x34b655…2a6f
2 touches
0 conflicts
0x230674a7…d5e5
0x34b655…2a6f
2 touches
0 conflicts
0x24b6091e…d294
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
0xcbcc67c0b7…8b34de
Audit this contract →
← previous block
·
next block →
recent activity