pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,739,361
← previous block
next block →
recent activity
Analyzing
Block #89,739,361
9 transactions · 9 stateful · 2026-07-23 21:32:55 UTC
Parallelism
67
/100
Blocked
33
%
Avg conflicts / tx
0.56
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,739,361
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5a5d9a99
#2
execFwdPositionOps
· blocks 3
#6
0x6a6288ff
#7
setData
#8
execOrders
#3
execFwdPositionOps
· blocks 2
#4
execFwdPositionOps
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcfb570f…cf1c
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x170f3b5b…db60
0x34b655…2a6f
4 touches
1 conflict
0xcfc5013f…0e81
0x34b655…2a6f
4 touches
1 conflict
0x0110331c…b891
0x34b655…2a6f
4 touches
1 conflict
0x2e1f5171…ad2d
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x53699236…fede
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
0xfcfb570f6f…7ecf1c
Audit this contract →
← previous block
·
next block →
recent activity