pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,734,619
← previous block
next block →
recent activity
Analyzing
Block #89,734,619
10 transactions · 10 stateful · 2026-07-23 21:08:58 UTC
Parallelism
80
/100
Blocked
30
%
Avg conflicts / tx
0.3
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,734,619
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x5a5d9a99
· blocks 1
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 1
#7
setData
#8
execOrders
· blocks 1
#5
execFwdPositionOps
#6
execFwdPositionOps
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w0
5
w1
6
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x26e32e90…8827
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x53699236…fede
0x34b655…2a6f
4 touches
1 conflict
0x76196ad0…ce0c
0x34b655…2a6f
4 touches
1 conflict
0x91c4e3d2…e63d
0x34b655…2a6f
4 touches
1 conflict
0x94b46bd0…e95d
0x34b655…2a6f
4 touches
1 conflict
0xb83387da…d672
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
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity