pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,719,949
← previous block
next block →
recent activity
Analyzing
Block #90,719,949
10 transactions · 9 stateful · 2026-07-27 08:08:03 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,719,949
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x3f5c179b
#3
execFwdPositionOps
· blocks 2
#4
0x3f5c179b
#6
0xe9316489
#7
setData
#9
0xc7e3ec2c
#5
execFwdPositionOps
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7496bc22…8327
0x34b655…2a6f
4 touches
1 conflict
0x917f99a5…7989
0x34b655…2a6f
4 touches
1 conflict
0xd93edb3f…94ec
0x34b655…2a6f
4 touches
1 conflict
0xf6deafb5…5c25
0x34b655…2a6f
4 touches
1 conflict
0xfaf22814…27c8
0x34b655…2a6f
4 touches
1 conflict
0x03cf7ec2…ef5a
0x34b655…2a6f
4 touches
1 conflict
0x11f90b22…bea4
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
0x7496bc22f9…e38327
Audit this contract →
← previous block
·
next block →
recent activity