pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,540,871
← previous block
next block →
recent activity
Analyzing
Block #89,540,871
10 transactions · 10 stateful · 2026-07-23 01:41:09 UTC
Parallelism
70
/100
Blocked
30
%
Avg conflicts / tx
0.5
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,540,871
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x6ad2e98b
#2
execFwdPositionOps
· blocks 3
#4
updateDataFeedsValuesPartial
#5
0x3f5c179b
#8
0x6a6171ac
#9
setData
#3
execFwdPositionOps
· blocks 1
#6
execFwdPositionOps
· blocks 1
#7
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf607560e…828a
0x34b655…2a6f
6 touches
3 conflicts
0x86cea35b…bdff
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…7223
0x34b655…2a6f
4 touches
1 conflict
0xbd92eaf4…4ed1
0x34b655…2a6f
4 touches
1 conflict
0xda27c764…7fab
0x34b655…2a6f
4 touches
1 conflict
0xe1a1a29a…a398
0x34b655…2a6f
4 touches
1 conflict
0xee6c163d…74ef
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
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
0xf607560e69…3f828a
Audit this contract →
← previous block
·
next block →
recent activity